Virtualization of vendor specific network interfaces of self-virtualizing input/output device virtual functions

• US 8,561,065 B2
• Filed: 11/15/2010
• Issued: 10/15/2013
• Est. Priority Date: 11/15/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cunningham, James B., De Leon, Baltazar III, Graham, Charles S., King, Brian J., Koch, Andrew T., Lucke, Kyle A., Whitney, Kristopher C.
• Primary Examiner(s): To, Jennifer
• Assistant Examiner(s): TEETS, BRADLEY A
• Application Number:
  US12/946,316
• Publication Number:
  US 20120124572A1
• Time in Patent Office: 1,065 Days
• Field of Search: None
• US Class Current: 718/1
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/545 where tasks reside in different layers, e.g. user- and kernel-space

Abstract

A vendor independent partition interface between a logical partition and an adjunct partition associated with a self-virtualizing IO resource is used to effectively abstract away vender-specific interface details for the self-virtualizing IO resource. By doing so, vender-specific implementation details may be isolated from the operating systems resident in logical partitions, thus requiring only changes in vendor specific firmware in order to support new or revised self-virtualizing IO resources.

Claims

1. A method of accessing a self-virtualizing input/output (IO) resource with multiple logical partitions in a data processing system, the method comprising:

interfacing a logical partition of the multiple logical partitions to an associated adjunct partition through a vendor-independent virtual network partition interface, the adjunct partition including a vendor independent server virtual network partition interface device driver configured to interface with the logical partition and a resource-specific device driver configured to interface with a virtual function or queue pair of the self-virtualizing IO resource, wherein the virtual partition interface interfaces the client virtual partition interface device driver with the server virtual partition interface device driver; and

in the logical partition, accessing the self-virtualizing IO resource by communicating with the vendor independent server virtual network partition interface device driver over the vendor-independent virtual network partition interface using a vendor-independent client virtual network partition interface device driver resident in the logical partition,

wherein each of the multiple logical partitions is interfaced to the self-virtualizing IO resource through an associated adjunct partition, wherein each adjunct partition couples the associated logical partition to one of a virtual function or a queue pair of the self-virtualizing IO resource, and wherein the adjunct partition includes a separate dispatchable state and employs a virtual address space donated from the logical partition or a hypervisor of the data processing system.

2. The method of claim 1, wherein interfacing the logical partition to the associated adjunct partition comprises interfacing the adjunct partition to an associated virtual function of the self-virtualizing IO resource, and wherein the self-virtualizing IO resource further comprises a physical function, the method further comprising:

interfacing a physical function adjunct partition with the physical function of the self-virtualizing IO resource; and

using the physical function adjunct partition to create the adjunct partition interfacing the logical partition to the virtual function.

3. The method of claim 1, wherein the self-virtualizing IO resource comprises a function with multiple queue pairs associated therewith, wherein interfacing the logical partition to the associated adjunct partition comprises interfacing the adjunct partition to an associated queue pair of the self-virtualizing IO resource, the method further comprising:

interfacing a function adjunct partition with the function of the self-virtualizing IO resource.

4. The method of claim 1, further comprising interfacing the vendor independent server virtual network partition interface device driver and the resource-specific device driver through a device driver application programming interface (API).

5. The method of claim 1, wherein the self-virtualizing IO resource comprises a single root input/output virtualization (SRIOV) Ethernet adapter.

6. An apparatus, comprising:

at least one processor; and

program code configured upon execution by the at least one processor to interface a self-virtualizing input/output (IO) resource with multiple logical partitions in a data processing system by interfacing a logical partition of the multiple logical partitions to an associated adjunct partition through a vendor-independent virtual network partition interface, wherein the adjunct partition includes a vendor independent server virtual network partition interface device driver configured to interface with the logical partition and a resource-specific device driver configured to interface with a virtual function or queue pair of the self-virtualizing IO resource, wherein the virtual partition interface interfaces the client virtual partition interface device driver with the server virtual partition interface device driver, and wherein the vendor-independent server virtual network partition interface device driver is configured to communicate over the vendor-independent virtual network partition interface with a vendor-independent client virtual network partition interface device driver resident in the logical partition;

wherein each of the multiple logical partitions is interfaced to the self-virtualizing IO resource through an associated adjunct partition, wherein each adjunct partition couples the associated logical partition to one of a virtual function or a queue pair of the self-virtualizing IO resource, and wherein the adjunct partition includes a separate dispatchable state and employs a virtual address space donated from the logical partition or a hypervisor of the data processing system.

7. The apparatus of claim 6, wherein the program code is configured to interface the logical partition to the associated adjunct partition by interfacing the adjunct partition to an associated virtual function of the self-virtualizing IO resource, wherein the self-virtualizing IO resource further comprises a physical function, and wherein the program code is further configured to interface a physical function adjunct partition with the physical function of the self-virtualizing IO resource, and to use the physical function adjunct partition to create the adjunct partition interfacing the logical partition to the virtual function.

8. The apparatus of claim 6, wherein the self-virtualizing IO resource comprises a function with multiple queue pairs associated therewith, wherein the program code is configured to interface the logical partition to the associated adjunct partition by interfacing the adjunct partition to an associated queue pair of the self-virtualizing IO resource, and wherein the program code is further configured to interface a function adjunct partition with the function of the self-virtualizing IO resource.

9. The apparatus of claim 6, wherein the program code is further configured to interface the vendor independent server virtual network partition interface device driver and the resource-specific device driver through a device driver application programming interface (API).

10. The apparatus of claim 6, wherein the self-virtualizing IO resource comprises a single root input/output virtualization (SRIOV) Ethernet adapter.

11. A program product, comprising:

a non-transitory computer readable medium; and

program code stored on the computer readable medium and configured upon execution to interface a self-virtualizing input/output (IO) resource with multiple logical partitions in a data processing system by interfacing a logical partition of the multiple logical partitions to an associated adjunct partition through a vendor-independent virtual network partition interface, wherein the adjunct partition includes a vendor independent server virtual network partition interface device driver configured to interface with the logical partition and a resource-specific device driver configured to interface with a virtual function or queue pair of the self-virtualizing IO resource, wherein the virtual partition interface interfaces the client virtual partition interface device driver with the server virtual partition interface device driver, and wherein the vendor-independent server virtual network partition interface device driver is configured to communicate over the vendor-independent virtual network partition interface with a vendor-independent client virtual network partition interface device driver resident in the logical partition;

wherein each of the multiple logical partitions is interfaced to the self-virtualizing IO resource through an associated adjunct partition, wherein each adjunct partition couples the associated logical partition to one of a virtual function or a queue pair of the self-virtualizing IO resource, and wherein the adjunct partition includes a separate dispatchable state and employs a virtual address space donated from the logical partition or a hypervisor of the data processing system.

12. The program product of claim 11, wherein the program code is configured to interface the logical partition to the associated adjunct partition by interfacing the adjunct partition to an associated virtual function of the self-virtualizing IO resource, wherein the self-virtualizing IO resource further comprises a physical function, and wherein the program code is further configured to interface a physical function adjunct partition with the physical function of the self-virtualizing IO resource, and to use the physical function adjunct partition to create the adjunct partition interfacing the logical partition to the virtual function.

13. The program product of claim 11, wherein the self-virtualizing IO resource comprises a function with multiple queue pairs associated therewith, wherein the program code is configured to interface the logical partition to the associated adjunct partition by interfacing the adjunct partition to an associated queue pair of the self-virtualizing IO resource, and wherein the program code is further configured to interface a function adjunct partition with the function of the self-virtualizing IO resource.

14. The program product of claim 11, wherein the program code is further configured to interface the vendor independent server virtual network partition interface device driver and the resource-specific device driver through a device driver application programming interface (API).

15. The program product of claim 11, wherein the self-virtualizing IO resource comprises a single root input/output virtualization (SRIOV) Ethernet adapter.

16. A method of developing an adjunct partition for use in providing access to a self-virtualizing input/output (IO) resource by at least one logical partition in a data processing system, the method comprising:

developing a resource-specific device driver configured to interface with a virtual function or queue pair of the self-virtualizing IO resource;

packaging the resource-specific device driver in an adjunct partition along with a vendor-independent server virtual network partition interface device driver, the vendor-independent server virtual network partition interface device driver configured to communicate with a vendor independent client virtual network partition interface device driver resident in a logical partition over a vendor-independent virtual network partition interface, wherein the virtual partition interface interfaces the client virtual partition interface device driver with the server virtual partition interface device driver, wherein the adjunct partition is a firmware component, and wherein the adjunct partition includes a separate dispatchable state and employs a virtual address space donated from an associated logical partition or a hypervisor of the data processing system; and

testing the adjunct partition with the resource-specific device driver and vendor-independent server virtual network partition interface device driver packaged therein, wherein testing includes testing communications between the logical partition and the self-virtualizing IO resource using the adjunct partition.