Discovery and Capability Exchange Management in a Virtualized Computing Platform Utilizing a SR-IOV Adapter

• US 20100290467A1
• Filed: 05/12/2009
• Published: 11/18/2010
• Est. Priority Date: 05/12/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Machuca, Carol T., Recio, Renato J., Eisenhauer, Daniel G., Palm, Jeffrey W., Graham, Charles S.
• Granted Patent: US 8,208,396 B2
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: Y02D 30/00 Reducing energy consumption in communication networks

Abstract

In various embodiments a traffic class manager is a resource within a virtualized computer systems trusted entity (i.e. a hypervisor, trusted partition, etc.) which maps requirements from a platform management and associated network capabilities onto an SR-IOV adapter in order to appropriately allocate SR-IOV adapter and network resources to the virtualized computer partitions. In various embodiments the traffic class manager defines network traffic classes that meet the objectives of a platform administrator based on the capabilities of the SR-IOV adapter and the network attached to the adapter ports. Once the traffic classes are defined, in various embodiments, the traffic class manager enforces the assignment of a traffic class to a virtual interface queue pair within a partition.

Claims

1. A method of managing network traffic classes in a virtualized computing platform comprising:

determining the capabilities of a Single Root I/O Virtualization and Sharing enabled network adapter;

determining the capabilities of the network and associated network switches;

defining one or more traffic classes based on the shared capabilities of the Single Root I/O Virtualization and Sharing enabled network adapter and of the network and associated network switches;

assigning the one or more defined traffic classes to a partition within the virtualized computing platform; and

routing Link Layer Discovery Protocol (LLDP) packets based upon the LLDP Multicast Address or the Ethertype Field to a LLDP queue pair.

2. The method of claim 1 wherein determining the capabilities of the network and associated network switches further comprises:

determining the network discovery and capability exchange features of the network and associated network switches.

3. The method of claim 1 wherein assigning the one or more defined traffic classes to a partition within the virtualized computing platform further comprises:

assigning the one or more defined traffic classes to a virtual interface queue pair (VIQP) within the partition.

4. The method of claim 1 wherein determining the capabilities of a Single Root I/O Virtualization and Sharing enabled network adapter further comprises:

determining Quality of Service (QoS) capabilities of the Single Root I/O Virtualization and Sharing enabled network adapter.

5. The method of claim 4 further comprising:

providing the QoS capability of the Single Root I/O Virtualization and Sharing enabled network adapter to a virtualized computing platform manager.

6. The method of claim 1 wherein assigning the one or more defined traffic classes to a partition within the virtualized computing platform further comprises:

defining the partition within the virtualized computing platform; and

assigning the VIQP to the partition.

7. The method of claim 1 wherein defining one or more traffic classes based on the shared capabilities of the Single Root I/O Virtualization and Sharing enabled network adapter and of the network and associated network switches further comprises:

designating either a physical function or a virtual function as a particular virtual interface.

8. The method of claim 1 wherein packets are routed based upon the particular virtual interface.

9. A virtualized computing platform for transferring commands to a network comprising:

a central processing unit (CPU);

a memory connected to the central processing unit;

a network and associated network switch attached to the central processing unit and memory;

a trusted entity configured to abstract at least the CPU and memory to allow for the presentation of a distinct virtual computing system within a partition amongst a plurality of partitions;

a Single Root I/O Virtualization and Sharing (SR-IOV) enabled network adapter connected between the network and the central processing unit and memory; and

a traffic class manager configured to map requirements designated at least in part by a virtualized computing platform manager and by the capabilities of the network switch onto the SR-IOV adapter.

10. The virtualized computing platform of claim 9 wherein the traffic class manager further comprises a LLDP queue pair and is configured to receive LLDP packets routed to the LLDP queue pair based upon the LLDP Multicast Address or the Ethertype Field.

11. The virtualized computing platform of claim 10 wherein the traffic class manager is further configured to determine the network discovery and capability exchange features of the network and associated network switches.

12. The virtualized computing platform of claim 11 wherein the traffic class manager is further configured to determine one or more network traffic classes based upon the capabilities of the SR-IOV adapter and upon the capabilities of the network and associated network switches.

13. The virtualized computing platform of claim 12 wherein the trusted entity further comprises:

a virtual interface queue pair (VIQP) configured to transmit and receive packets to or from the network utilizing an SR-IOV physical function or virtual function.

14. The virtualized computing platform of claim 13 wherein the virtualized computing platform manager assigns the VIQP to utilize the determined one or more network traffic classes.

15. The virtualized computing platform of claim 14 wherein the virtualized computing platform manager further assigns the VIQP to a partition.

16. The virtualized computing platform of claim 15 wherein the traffic class manager further enforces the assignment of the one or more traffic classes to the VIQP.

17. The virtualized computing platform of claim 16 wherein the traffic class manager is configured to accept ingress Link Layer Discovery Protocol (LLDP) Data Units (PDUs) and is configured to build and sends egress LLDP PDUs.

18. The virtualized computing platform of claim 17 wherein the traffic class manager is configured to implement a data center discovery and capability exchange protocol (DCBX) control state machine, is configured to parse ingress DCBX Type Length Value (TLV) by feature sub-TLV, and is configured to build egress DCBX TLVs.

19. The virtualized computing platform of claim 18 wherein the traffic class manager is configured to provide the DCBX feature state machine, is configured to manage a priority group configuration table, and is configured to manage a priority-based flow control structure.

20. The virtualized computing platform of claim 9 wherein the SR-IOV adapter is configured to designate either a physical function or a virtual function as a particular virtual interface.