Method and system for configuring device driver by selecting a plurality of component drivers to be included in the device driver

• US 5,781,797 A
• Filed: 09/30/1992
• Issued: 07/14/1998
• Est. Priority Date: 09/30/1992
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Shah, Shishir, Crick, Andrew P. R., Shea, Thomas J., Glass, Mike
• Primary Examiner(s): Meky, Moustafa M.
• Application Number:
  US07/954,920
• Time in Patent Office: 2,113 Days
• Field of Search: 395/275, 395/700, 395/712, 395/680-682, 395/882-885, 395/828, 395/830, 395/892, 395/651-653, 395/650, 395/500, 364/200, 364/900
• US Class Current: 710/10
• 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

A method and system for configuring and executing device drivers in a computer system is provided. In a preferred embodiment, the device drivers comprise a plurality of component drivers. Each component driver performs a function (e.g., disk caching) that may be used in accessing a device. The component drivers of a device driver are ordered from a top layer to a bottom layer. When accessing a device, the top layer component driver of the device driver is first invoked. Each component driver performs its function and invokes the next lower layer component driver. The bottom layer component driver interacts directly with the device. An operating system, preferably, dynamically configures the device drivers at computer system startup. The operating system has a plurality of component drivers that are available to be configured into a device driver. To configure a device driver, the operating system invokes each component driver to determine whether the component driver should be included as a layer in the device drive. If a component driver should be included, the component driver stores a reference to the component driver in a call-down table for the device driver. The call-down table stores the ordering of the component driver layers. When accessing the device, the operating system first invokes the component driver referenced by the top reference in the call-down table. Each component driver in turn invokes the component driver referenced by the next lower reference in the call-down table.

Claims

1. A method in a computer system of configuring a device driver for controlling access to a device, the method comprising the computer-implemented steps of:

defining a multiplicity of component drivers, each component driver for performing a function of a device driver; and

with the computer system, selecting a plurality of the component drivers to be included in the device driver, wherein the selected component drivers compose a configured device driver.

2. The method of claim 1 including the step of organizing the selected component drivers into layers composing the configured device driver.

3. The method of claim 1 or 2 wherein the step of selecting a plurality of component drivers to be included in the device driver invokes a component driver so that the component driver determines whether it should be selected to be included in the device driver.

4. The method of claim 1 or 2 wherein a component driver is selected to be included in the device driver based on device-specific information.

5. The method of claim 1 or 2 wherein a component driver is included in a plurality of device drivers.

6. The method of claim 2 wherein the step of organizing the selected component drivers stores a reference to each selected component driver in an entry in a call-down table, the table having an entry for each layer within the configured device driver, further comprising the steps of, under the control of each selected component driver except the selected component driver having a last entry in the call-down table, in response to the invocation of the device driver:

invoking the selected component driver having the next entry in the call-down table, and

after the component driver having the next entry in the call-down table completes its execution, returning from its invocation.

7. The method of claim 1 wherein the defining step includes the step of defining a compression component driver for compressing data, and wherein the selecting step includes the step of selecting the compression component driver to be included in the device driver.

8. The method of claim 1 wherein the defining step includes the step of defining a encryption component driver for encrypting data, and wherein the selecting step includes the step of selecting the encryption component driver to be included in the device driver.

9. A method in a computer system of executing a device driver for controlling access to a device, the device driver having component drivers, the component drivers being ordered from a top layer to a bottom layer, a reference to each component driver being contained in an ordered call-down table, the method comprising the steps of:

invoking the top layer component driver when accessing the device; and

for each component driver except for the bottom layer component driver, under the control of the component driver, invoking a next lower layer component driver upon completion of the component driver by retrieving the reference to the next lower layer component driver from the call-down table.

10. The method of claim 9 wherein the step of invoking the next ordered component driver is suppressed based on device-specific information.

11. A method in a computer system of configuring and executing a device driver for controlling access to a device, the method comprising the steps of:

organizing a plurality of component drivers as layers in the device driver by storing references to the component drivers in a call-down table; and

invoking each of the plurality of component drivers each time the device is accessed by retrieving the references from the call-down table.

12. The method of claim 11 wherein the component drivers are ordered from a top layer to a bottom layer and wherein each component driver invokes a next lower layer component driver using a reference stored in the call-down table.

13. The method of claim 11 where in the plurality of component drivers includes a component driver for compressing data, and wherein the organizing step includes the step of storing a reference to the component driver for compressing data in the call-down table, and wherein the invoking step includes the step of retrieving the reference to the component driver for compressing data from the call-down table.

14. The method of claim 11 where in the plurality of component drivers includes a component driver for encrypting data, and wherein the organizing step includes the step of storing a reference to the component driver for encrypting data in the call-down table, and wherein the invoking step includes the step of retrieving the reference to the component driver for encrypting data from the call-down table.

15. A computer system for configuring a device driver for controlling access to a device, the system comprising:

a multiplicity of component drivers, each component driver for performing a function of a device driver; and

means for selecting a plurality of the component drivers to be included in the device driver, wherein the selected component drivers compose a configured device driver.

16. The computer system of claim 15 including means for organizing selected component drivers into layers composing the configured device driver.

17. A computer system for executing a device driver for controlling access to a device, the device driver having component drivers, the component drivers being ordered from a top layer to a bottom layer, a reference to each component driver being contained in a call-down table the computer system comprising:

means for invoking the top layer component driver when accessing the device; and

means, within each component driver except for the bottom layer component driver, for invoking the next lower layer component driver, including means for retrieving the reference to the next lower layer component driver from the call-down table.

18. A computer method of configuring and executing a device driver for controlling access to a device, the method comprising the steps of:

for each component driver referenced in a load table;

loading the component driver,

passing to the loaded component driver a device control block of the device, and

linking the loaded component driver into a call-down table based on device-specific information contained in the device control block; and

invoking each component driver linked into the call-down table when accessing the device.

19. The method according to claim 18, wherein each invoked component driver invokes a next component driver linked in the call-down table.

20. A computer-readable memory containing a call-down table defining an invokable device driver dynamically configured from selected independent component drivers, the call-down table comprising a reference to each selected component driver, the references arranged in the order that the selected component drivers are to be invoked each time the configured device driver is invoked.

21. A method in a computer system for dynamically constructing a device driver, comprising the steps of:

retrieving an ordered list of available component drivers; and

for each available component driver, in the order of the retrieved list;

calling the component driver to determine whether the component driver should be incorporated in the device driver; and

if the component driver determines that it should be incorporated in the device driver, appending a reference to the component to a call-down table that may be used to invoke the constructed device driver.

22. The method of claim 21 wherein the call-down table comprises an ordered list of references to component drivers of the constructed device driver, further comprising the steps of:

receiving a request to invoke the device driver;

in response to the received request, using the first reference in the call-down table to invoke the component driver to which it refers; and

for each component driver except the component driver referred to by the last reference in the call-down table, under the control of the component driver, using the reference following the reference to the component driver in the call-down table to invoke the next component driver of the device driver.

23. The method of claim 22, further including the steps of:

for each component driver, returning from its invocation when its processing is complete; and

for at least one of the component drivers, performing additional processing after the component driver that it invoked returns and before returning from its own invocation.

24. The method of claim 21, further comprising the step of, in response to a user request, removing a component driver from the list of available component drivers, thereby rendering the removed component driver unavailable for inclusion in the device driver.

25. The method of claim 21, further comprising the step of, in response to a user request, adding a new component driver to the list of available component drivers, thereby making the new component driver available for inclusion in the device driver.

26. An instance of computer-readable media that causes a computer system to dynamically construct a device driver by performing the steps of:

retrieving an ordered list of available component drivers; and

for each available component driver, in the order of the retrieved list;

calling the component driver to determine whether the component driver should be incorporated in the device driver; and

if the component driver determines that it should be incorporated in the device driver, appending a reference to the component to a call-down table that may be used to invoke the constructed device driver.

27. The instance of computer-readable media of claim 26 wherein the contents of the instance of computer-readable media further cause the computer system to perform the steps of:

receiving a request to invoke the device driver;

in response to the received request, using the first reference in the call-down table to invoke the component driver to which it refers; and

for each component driver except the component driver referred to by the last reference in the call-down table, under the control of the component driver, using the reference following the reference to the component driver in the call-down table to invoke the next component driver of the device driver.

28. The instance of computer-readable media of claim 27 wherein the contents of the instance of computer-readable media further cause the computer system to perform the steps of:

for each component driver, returning from its invocation when its processing is complete; and

for at least one of the component drivers, performing additional processing after the component driver that it invoked returns and before returning from its own invocation.