Techniques for use with device drivers in a common software environment

• US 7,950,022 B1
• Filed: 06/29/2007
• Issued: 05/24/2011
• Est. Priority Date: 06/29/2007
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Brown, Jeffrey A., McCann, Peter J., Gould, Christopher M.
• Primary Examiner(s): Nguyen; Van H
• Application Number:
  US11/824,506
• Time in Patent Office: 1,425 Days
• Field of Search: 719/310, 719/321, 719/327, 719/328
• US Class Current: 719/327
• CPC Class Codes: G06F 13/102 where the programme performs an interfacing function, e.g. device driver G06F13/105 takes precedence; scheduling within device drivers G06F9/52; contention policies within device drivers G06F9/4881

Abstract

Described are techniques for facilitating communication between device drivers. A device driver is provided that makes at least one call using an application programming interface. The application programming interface facilitates communication between the device driver module and a target code module. The application programming interface provides support for performing the at least one call from a first execution mode associated with the device driver module and a second execution mode associated with the target code module. The application programming interface provides support for user space to user space communication, user space to kernel space communication, kernel space to kernel space communication, and kernel to user space communication. The first execution mode of the device driver module and said second execution mode of the target code module are determined. A communication path between the modules is established in accordance with said first execution mode and said second execution mode.

Claims

1. A computer-implemented method for facilitating communication between device drivers comprising:

providing a device driver module making at least one call using an application programming interface, the application programming interface facilitating communication between the device driver module and a target code module wherein the application programming interface provides support for performing the at least one call from a first execution mode associated with the device driver module and a second execution mode associated with the target code module, said application programming interface providing support for user space to user space communication, user space to kernel space communication, kernel space to kernel space communication, and kernel to user space communication;

determining, by code of the application programming interface, said first execution mode of the device driver module and said second execution mode of the target code module, wherein said first execution mode and said second execution mode are one of a user execution mode or a kernel execution mode; and

establishing, using code of the application programming interface, a communication path between said device driver module and said target code module in accordance with said first execution mode and said second execution mode.

2. The method of claim 1, wherein said device driver module performs a first call using the application programming interface to register a first interrupt service routine to be invoked upon the occurrence of an interrupt to a device associated with said device driver.

3. The method of claim 2, wherein the first interrupt service routine executes in said kernel execution mode.

4. The method of claim 3, wherein an interrupt occurs causing said first interrupt service routine to be invoked, said first interrupt service routine perform processing including:

acknowledging said interrupt;

saving device state information regarding said interrupt occurring for said device; and

performing a second call using said application programming interface for scheduling a deferred procedure call for execution.

5. The method of claim 4, wherein, if said device driver module is executing in said user execution mode, when said deferred procedure call executes, said deferred procedure call performs processing to signal a wait thread to resume execution, said wait thread executing in said user execution mode.

6. The method of claim 5, wherein said wait thread and said device driver module execute in a same user address space.

7. The method of claim 5, wherein, when said wait thread resumes execution, said wait thread performs processing including:

invoking a second interrupt service routine included in said device driver module.

8. The method of claim 7, wherein said second interrupt service routine performs processing including:

servicing said interrupt.

9. The method of claim 8, wherein said second interrupt service routine performs processing including:

scheduling a deferred procedure call for execution to perform additional processing to service said interrupt.

10. The method of claim 4, wherein, if said device driver module is executing in said kernel execution mode, when said deferred procedure call executes, said deferred procedure call performs processing to invoke a second interrupt service routine included in said device driver module.

11. The method of claim 10, wherein said second interrupt service routine performs processing including:

scheduling a deferred procedure call for execution to perform additional processing to service said interrupt.

12. The method of claim 4, wherein, when said device driver module including said interrupt service routine is executing in user execution mode, said second call performs processing to emulate deferred procedure call processing, and wherein when said device driver module including said interrupt service routine is executing in kernel execution mode, said second call performs processing including using an operating system primitive for scheduling a deferred procedure call.

13. The method of claim 7, wherein, when said wait thread resumes execution, said wait thread performs processing including:

taking a write lock prior to performing said invoking; and

releasing said write lock after performing said invoking, said write lock being used to emulate enabling and disabling interrupt processing, wherein if said wait thread is unable to take said write lock, interrupt processing is disabled, and if said wait thread is able to take said write lock, interrupt processing is enabled.

14. The method of claim 1, wherein said same device driver module is used when said device driver executes in said user execution mode and when said device driver executes in said kernel execution mode.

15. A data storage system comprising a computer readable medium with executable code stored thereon for facilitating communication between device drivers, the computer readable medium comprising executable code for:

providing a device driver module making at least one call using an application programming interface, the application programming interface facilitating communication between the device driver module and a target code module wherein the application programming interface provides support for performing the at least one call from a first execution mode associated with the device driver module and a second execution mode associated with the target code module, said application programming interface providing support for user space to user space communication, user space to kernel space communication, kernel space to kernel space communication, and kernel to user space communication;

determining, by code of the application programming interface, said first execution mode of the device driver module and said second execution mode of the target code module, wherein said first execution mode and said second execution mode are one of a user execution mode or a kernel execution mode; and

establishing, using code of the application programming interface, a communication path between said device driver module and said target code module in accordance with said first execution mode and said second execution mode.

16. The data storage system of claim 15, wherein said data storage system includes a plurality of processors, each of said processors executing a different instance of said device driver module.

17. The data storage system of claim 15, wherein said data storage system includes a plurality of instances of said device driver module, each of said instances executing in user execution mode and each of said instances having its own user process address space.

18. The data storage system of claim 17, wherein, upon failure of a first of a first of said instances, a second of said instances handles processing of requests currently being serviced by said first instance when said first instance failed.

19. A computer readable medium comprising code stored thereon for facilitating communication between device drivers, the computer readable medium comprising code that:

provides a device driver module making at least one call using an application programming interface, the application programming interface facilitating communication between the device driver module and a target code module wherein the application programming interface provides support for performing the at least one call from a first execution mode associated with the device driver module and a second execution mode associated with the target code module, said application programming interface providing support for user space to user space communication, user space to kernel space communication, kernel space to kernel space communication, and kernel to user space communication;

determines, by code of the application programming interface, said first execution mode of the device driver module and said second execution mode of the target code module, wherein said first execution mode and said second execution mode are one of a user execution mode or a kernel execution mode; and

establishes, using code of the application programming interface, a communication path between said device driver module and said target code module in accordance with said first execution mode and said second execution mode.

20. The computer readable medium of claim 19, wherein said device driver module performs a first call using the application programming interface to register a first interrupt service routine to be invoked upon the occurrence of an interrupt to a device associated with said device driver, the first interrupt service routine executes in said kernel execution mode, and wherein an interrupt occurs causing said first interrupt service routine to be invoked, said first interrupt service routine includes code stored on the computer readable medium that performs processing including acknowledging said interrupt, saving device state information regarding said interrupt occurring for said device, and performing a second call using said application programming interface for scheduling a deferred procedure call for execution.