Input/output request packet handling techniques by a device specific kernel mode driver

• US 9,331,869 B2
• Filed: 03/04/2010
• Issued: 05/03/2016
• Est. Priority Date: 03/04/2010
• Status: Active Grant

• Current Assignee: NVIDIA Corporation
• Original Assignee: NVIDIA Corporation
• Inventors: Zhu, Timothy, Dunn, David, Spurlock, Randy, Spacie, Thomas
• Primary Examiner(s): Truong, Lechi
• Application Number:
  US12/717,142
• Publication Number:
  US 20110216780A1
• Time in Patent Office: 2,252 Days
• Field of Search: 719/310, 719/321
• US Class Current: 1/1
• 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
• CPC Class Codes: H04L 12/56 Packet switching systems

Abstract

The input/output request packet (IRP) handling technique includes determining if a received input/output request packet should receive a given handling. If the input/output request packet should receive the given handling, the input/output request packet is dispatched to a device specific dispatch input/output request packet handler. Otherwise, the input/output request packet is redirected to an operating system dispatch input/output request packet handler.

Claims

1. One or more non-transitory computing device readable media having computing device executable instructions which when executed perform a method comprising:

receiving, by a device specific kernel mode driver, a dispatch table including a pluralityy of input/output manager function pointers;

sending, by the device specific kernel mode driver to an operating system kernel mode driver, the dispatch table including the plurality of input/output manager function pointers;

receiving, by the device specific kernel mode driver, a dispatch table including the plurality of input/output manager function pointers and a plurality of operating system function pointers;

storing, by the device specific kernel mode driver, the dispatch table including the plurality of input/output manager function pointers and the plurality of operating system function pointers;

creating, by the device specific kernel mode driver, a dispatch table including the plurality of input/output manager function pointers and the plurality of operating system functions wherein one or more of the operating system function pointers are replaced by one or more device specific kernel mode driver function pointers;

sending, by the device specific kernel mode driver to an input/output manager, the dispatch table including, the plurality of input/output manager function pointers and the plurality of operating system functions wherein one or more of the operating system function pointers are replaced by one or more device specific kernel mode driver function pointers;

receiving, by a device specific kernel mode driver, a input/output request packet from the input/output manager based on the dispatch table including the plurality of input/output manager function pointers and the plurality of operating system functions wherein one or more of the operating system function pointers are replaced by one or more device specific kernel mode driver function pointers from the device specific kernel mode driver to the input/output manager;

determining, by the device specific kernel mode driver, if the input/output request packet is to receive a given handling;

dispatching, by the device specific kernel mode driver using an operating system function pointer in the dispatch table stored by the device specific kernel mode driver, the input/output request packet to a device specific dispatch input/output request packet handler if the input/output request packet is to receive the given handling; and

redirecting, by the device specific kernel mode driver using an operating system function pointer in the dispatch table stored by the device specific kernel mode driver, the input/output request packet to an operating system dispatch input/output request packet handler if the input/output request packet is not to receive the given handling.

2. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 1, wherein the input/output request packet is to receive the given handling the input/output request packet comprises a power type input/output request packet.

3. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 1, wherein the input/output request packet is to receive the given handling if the input/output request packet comprises a plug-and-play type input/output request packet.

4. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 1, wherein the input/output request is for a secondary graphics processing unit of a computing device including a primary graphics processing unit.

5. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 4, wherein the primary graphics processing unit and the secondary graphics processing unit are heterogeneous graphics processing units.

6. The one or more non-transitory computing device readable media having computing, device executable instructions which when executed perform the method of claim 1, wherein determining if the input/output request packet should receive a given handling comprises calling a dispatch function;

local to the device specific kernel mode driver, to determine a content of the input/output request packet.

7. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 1, further comprising calling, by the device specific dispatch handler, a corresponding function for the input/output request packet if the input/output request packet is to receive the given handling.

8. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 1, further comprising calling, by the device specific dispatch handler, a corresponding driver for the input/output request packet if the input/output request packet is to receive the given handling.

9. One or more non-transitory computing device readable media having, computing device executable instructions which when executed perform a method comprising:

passing a dispatch table including a plurality of input/output manager function pointers from an input/output manager to a device specific kernel mode driver;

passing the dispatch table including the plurality of input/output manager function pointers from the device specific kernel mode driver to an operating system kernel mode driver;

passing a dispatch table including the plurality of input/output manager function pointers and a plurality of operating system function pointers from the operating system kernel mode driver to the device specific kernel mode driver;

storing the dispatch table including the plurality of input/output manager function pointers and the plurality of operating system function pointers in a dispatch table of device specific kernel mode driver;

passing a dispatch table including the plurality of input/output manager function pointers and the plurality of operating system functions wherein one or more of the operating system function pointers are replaced by one or more device specific kernel, mode driver function pointers from the device specific kernel mode driver to the input/output manager;

passing a input/output request packet from the input/output manager to a dispatch function of the device specific kernel mode driver based on the dispatch table including the plurality of input/output manager function pointers and the plurality of operating system functions wherein one or more of the operating system function pointers are replaced by one or more device specific kernel mode driver function pointers from the device specific kernel mode driver to the input/output manager;

determining, by the dispatch function, if the input/output request packet should receive a given handling;

dispatching the input/output request packet from the dispatch function to a device specific dispatch input/output request packet handler if the input/output request packet is to receive the given handling; and

redirecting the input/output request packet from the dispatch function to an operating system dispatch input/output request packet handler if the input/output request packet is not to receive the given handling.

10. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 9, wherein the input/output request packet is to receive the given handling if the input/output request packet comprises a power type input/output request packet.

11. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 9, wherein the given handling comprises a power control function.

12. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 9, wherein determining if the input/output request packet should receive a given handling comprises calling a dispatch function, local to the device specific kernel mode driver, to determine a content of the input/output request packet.

13. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 9, further comprising calling, by the device specific dispatch handler, a corresponding function for the input/output request packet if the input/output request packet is to receive the given handling.

14. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 9, further comprising calling, by the device specific dispatch handler, a corresponding driver for the input/output request packet if the input/output request packet is to receive the given handling.

15. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 9, wherein the input/output request is for a discrete graphics processing unit of a computing device including an integrated graphics processing unit.

16. The one or more non-transitory computing device readable media having computing device executable instructions which when executed perform the method of claim 15, wherein the discrete graphics processing unit and the integrated graphics processing unit are heterogeneous graphics processing units.