Abstract:
A method of controlling bandwidth including receiving and classifying a packet, sending the packet to a hardware receive ring based on a classification of the packet, and sending, in accordance with an operating mode, the packet to a software receive ring, sending the packet from the software receive ring to a virtual network interface card, where the virtual network interface card is associated with a virtual machine, where the operating mode is adjusted to control the bandwidth consumed by the virtual machine.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    The present application contains subject matter that may be related to the subject matter in the following U.S. applications filed on Apr. 22, 2005, and assigned to the assignee of the present application: “Method and Apparatus for Managing and Accounting for Bandwidth Utilization Within A Computing System” with U.S. application Ser. No. 11/112,367 (Attorney Docket No. 03226/643001; SUN050681); “Method and Apparatus for Consolidating Available Computing Resources on Different Computing Devices” with U.S. application Ser. No. 11/112,368 (Attorney Docket No. 03226/644001; SUN050682); “Assigning Higher Priority to Transactions Based on Subscription Level” with U.S. application Ser. No. 11/112,947 (Attorney Docket No. 03226/645001; SUN050589); “Method and Apparatus for Dynamically Isolating Affected Services Under Denial of Service Attack” with U.S. application Ser. No. 11/112,158 (Attorney Docket No. 03226/646001; SUN050587); “Method and Apparatus for Improving User Experience for Legitimate Traffic of a Service Impacted by Denial of Service Attack” with U.S. application Ser. No. 11/112,629 (Attorney Docket No. 03226/647001; SUN050590); “Method and Apparatus for Limiting Denial of Service Attack by Limiting Traffic for Hosts” with U.S. application Ser. No. 11/112,328 (Attorney Docket No. 03226/648001; SUN050591); “Hardware-Based Network Interface Per-Ring Resource Accounting” with U.S. application Ser. No. 11/112,222 (Attorney Docket No. 03226/649001; SUN050593); “Dynamic Hardware Classification Engine Updating for a Network Interface” with U.S. application Ser. No. 11/112,934 (Attorney Docket No. 03226/650001; SUN050592); “Network Interface Card Resource Mapping to Virtual Network Interface Cards” with U.S. application Ser. No. 11/112,063 (Attorney Docket No. 03226/651001; SUN050588); “Network Interface Decryption and Classification Technique” with U.S. application Ser. No. 11/112,436 (Attorney Docket No. 03226/652001; SUN050596); “Method and Apparatus for Enforcing Resource Utilization of a Container” with U.S. application Ser. No. 11/112,910 (Attorney Docket No. 03226/653001; SUN050595); “Method and Apparatus for Enforcing Packet Destination Specific Priority Using Threads” with U.S. application Ser. No. 11/112,584 (Attorney Docket No. 03226/654001; SUN050597); “Method and Apparatus for Processing Network Traffic Associated with Specific Protocols” with U.S. application Ser. No. 11/112,228 (Attorney Docket No. 03226/655001; SUN050598). 
         [0002]    The present application contains subject matter that may be related to the subject matter in the following U.S. applications filed on Oct. 21, 2005, and assigned to the assignee of the present application: “Method and Apparatus for Defending Against Denial of Service Attacks” with U.S. application Ser. No. 11/255,366 (Attorney Docket No. 03226/688001; SUN050966); “Router Based Defense Against Denial of Service Attacks Using Dynamic Feedback from Attacked Host” with U.S. application Ser. No. 11/256,254 (Attorney Docket No. 03226/689001; SUN050969); and “Method and Apparatus for Monitoring Packets at High Data Rates” with U.S. application Ser. No. 11/226,790 (Attorney Docket No. 03226/690001; SUN050972). 
         [0003]    The present application contains subject matter that may be related to the subject matter in the following U.S. applications filed on Jun. 30, 2006, and assigned to the assignee of the present application: “Network Interface Card Virtualization Based On Hardware Resources and Software Rings” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/870001; SUN061020); “Virtual Switch” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/873001; SUN061023); “System and Method for Virtual Network Interface Cards Based on Internet Protocol Addresses” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/874001; SUN061024); “Virtual Network Interface Card Loopback Fastpath” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/876001; SUN061027); “Bridging Network Components” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/877001; SUN061028); “Reflecting the Bandwidth Assigned to a Virtual Network Interface Card Through Its Link Speed” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/878001; SUN061029); “Method and Apparatus for Containing a Denial of Service Attack Using Hardware Resources on a Virtual Network Interface Card” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/879001; SUN061033); “Virtual Network Interface Cards with VLAN Functionality” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/882001; SUN061037); “Method and Apparatus for Dynamic Assignment of Network Interface Card Resources” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/883001; SUN061038); “Generalized Serialization Queue Framework for Protocol Processing” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/884001; SUN061039); “Serialization Queue Framework for Transmitting Packets” with U.S. application Ser. No. TBD (Attorney Docket No. 03226/885001; SUN061040). 
     
     BACKGROUND 
       [0004]    Network traffic is transmitted from a network, such as the Internet, from a sending system (e.g., a computer system) to a receiving system (e.g., a computer system) via a network interface card (NIC). The NIC is a piece of hardware found in a typical computer system that includes functionality to send and receive network traffic. Typically, network traffic is transmitted in the form of packets, where each packet includes a header and a payload. The header contains information regarding the source address, destination address, size, transport protocol used to transmit the packet, and various other identification information associated with the packet. The payload contains the actual data to be transmitted from the network to the receiving system. 
         [0005]    Each of the packets sent between the sending system and receiving system is typically associated with a connection. The connection ensures that packets from a given process on the sending system reach the appropriate process on the receiving system. Packets received by the receiving system (via a NIC associated with the receiving system) are analyzed by a classifier to determine the connection associated with the packet. 
         [0006]    Typically, the classifier includes a connection data structure that includes information about active connections on the receiving system. The connection data structure may include the following information about each active connection: (i) the queue associated with the connection; and (ii) information necessary to process the packets on the queue associated with the connection. Depending on the implementation, the connection data structure may include additional information about each active connection. Such queues are typically implemented as first-in first-out (FIFO) queues and are bound to a specific central processing unit (CPU) on the receiving computer system. Thus, all packets for a given connection are placed in the same queue and are processed by the same CPU. In addition, each queue is typically configured to support multiple connections. 
       SUMMARY 
       [0007]    In general, in one aspect, the invention relates to a method of controlling bandwidth including receiving and classifying a packet, sending the packet to a hardware receive ring based on a classification of the packet, and sending, in accordance with an operating mode, the packet to a software receive ring, sending the packet from the software receive ring to a virtual network interface card, where the virtual network interface card is associated with a virtual machine, where the operating mode is adjusted to control the bandwidth consumed by the virtual machine. 
         [0008]    In general, in one aspect, the invention relates to a system for controlling bandwidth including a network interface card including a plurality of hardware receive rings, a classifier configured to classify a packet and sending the packet to one of the plurality of hardware rings based on a classification, and a host, operatively connected to the network interface card, including a virtual network interface card associated with a virtual machine, a software receive ring associated with the virtual network interface card and at least one of the plurality of hardware receive rings, where the packet is sent from the hardware receive ring to the software receive ring based on an operating mode of the software receive ring, where the operating mode is adjusted to control the bandwidth consumed by the virtual machine. 
         [0009]    Other aspects of the invention will be apparent from the following description and the appended claims. 
     
     
       BRIEF DESCRIPTION OF DRAWINGS 
         [0010]      FIG. 1  shows a computer system in accordance with one or more embodiments of the invention. 
           [0011]      FIGS. 2 and 3  show flow charts in accordance with one or more embodiments of the invention. 
           [0012]      FIG. 4  shows a computer system in accordance with one or more embodiments of the invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0013]    Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency. 
         [0014]    In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description. 
         [0015]    In general, embodiments of the invention provide a method and system for controlling the bandwidth consumed by a virtual machine. More specifically, embodiments of the invention relate to a method and system for controlling bandwidth using software receive rings. 
         [0016]      FIG. 1  shows a system in accordance with one embodiment of the invention. As shown in  FIG. 1 , the system includes a host ( 101 ) operatively connected to a NIC ( 102 ). The NIC ( 102 ) provides an interface between the host ( 101 ) and a network (not shown) (e.g., a local area network, a wide area network, a wireless network, etc.). More specifically, the NIC ( 102 ) includes a network interface (NI) (i.e., the hardware on the NIC used to interface with the network) (not shown). For example, the NI may correspond to an RJ-45 connector, a wireless antenna, etc. The packets received by the NI are then sent to other components on the NIC ( 102 ) for processing. In one embodiment of the invention, the NIC ( 102 ) includes a classifier ( 155 ) and one or more hardware receive rings ( 145 ,  150 ). In one embodiment of the invention, the hardware receive rings ( 145 ,  150 ) correspond to portions of memory within the NIC ( 102 ) used to temporarily store the received packets. Further, in one embodiment of the invention, a ring element of the receive rings ( 145 ,  150 ) may point to host memory. In one embodiment of the invention, the classifier ( 155 ) is configured to analyze the incoming network traffic, typically in the form of packets, received from the network (not shown). 
         [0017]    In one embodiment of the invention, analyzing individual packets includes determining to which of the hardware receive rings ( 145 ,  150 ) each packet is sent. In one embodiment of the invention, analyzing the packets by the classifier ( 155 ) includes analyzing one or more fields in each of the packets to determine to which of the hardware receive rings ( 145 ,  150 ) the packets are sent. As an alternative, the classifier ( 155 ) may use the contents of one or more fields in each packet as an index into a data structure that includes information necessary to determine to which hardware receive ring ( 145 ,  150 ) that packet is sent. The classifier ( 155 ) may be implemented entirely in hardware (i.e., the classifier ( 155 ) may be a separate microprocessor embedded on the NIC ( 102 )). Alternatively, the classifier ( 155 ) may be implemented in software stored in memory (e.g., firmware, etc.) on the NIC and executed by a microprocessor on the NIC ( 102 ). 
         [0018]    In one embodiment of the invention, the host ( 101 ) may include the following components: a device driver ( 140 ), one or more software receive rings ( 130 ,  135 ), one or more virtual NICs ( 120 ,  125 ), and one or more virtual machines ( 105 ,  110 ) containing one or more virtual stacks ( 106 ,  111 ). In one embodiment of the invention, the device driver ( 140 ) provides an interface between the hardware receive rings ( 145 ,  150 ) and the host ( 101 ). More specifically, the device driver ( 140 ) exposes the hardware receive rings ( 145 ,  150 ) to the host ( 101 ). 
         [0019]    In one embodiment of the invention, each of the software receive rings ( 130 ,  135 ) is associated with one or more hardware receive rings ( 145 ,  150 ). In one embodiment of the invention, there is a one-to-one mapping of hardware receive rings ( 145 ,  150 ) to software receive rings ( 130 ,  135 ). In one embodiment of the invention, a packet may flow from a hardware receive ring ( 145 ,  150 ) to a virtual NIC ( 120 ,  125 ) through a software receive ring ( 130 ,  135 ). In other words, the software receive ring ( 130 ,  135 ) corresponds to a buffer interposed between a hardware receive ring ( 145 ,  150 ) and a virtual NIC ( 120 ,  125 ). Alternatively, the software receive ring ( 130 ,  135 ) corresponds to a FIFO queue interposed between a hardware receive ring ( 145 ,  150 ) and a virtual NIC ( 120 ,  125 ). 
         [0020]    In one embodiment of the invention, a software receive ring ( 130 ,  135 ) may be capable of determining the bandwidth consumed by a virtual machine ( 105 ,  110 ) by analyzing the number and/or contents of packets flowing from a hardware receive ring ( 145 ,  150 ) to the software receive ring ( 130 ,  135 ) (and, thus, to the virtual machine associated with the software receive ring). In one embodiment of the invention, each software receive ring ( 130 ,  135 ) is capable of adjusting the operating mode of the one or more hardware receive rings ( 145 ,  150 ) based on bandwidth consumption (discussed below). Further, in one embodiment of the invention, each software receive ring ( 130 ,  135 ) is configured to regulate the flow of packets from the NIC ( 102 ) to the virtual NICs ( 120 ,  125 ) based on its operating mode (discussed below). In one embodiment of the invention, each software receive ring ( 130 ,  135 ) is implemented in the Media Access Control (MAC) layer (not shown) of the host ( 101 ). 
         [0021]    In one or more embodiments of the invention, each of the virtual NICs ( 120 ,  125 ) is associated with a software receive ring ( 130 ,  135 ). The virtual NICs ( 120 ,  125 ) provide an abstraction layer between the NIC ( 102 ) and the various packet destinations (not shown) executing on the virtual machines ( 105 ,  110 ) of the host ( 101 ). More specifically, each virtual NIC ( 120 ,  125 ) operates like a NIC ( 102 ). For example, in one embodiment of the invention, each virtual NIC ( 120 ,  125 ) is associated with one or more Internet Protocol (IP) addresses, one or more ports, and configured to handle one or more protocol types. Thus, while the host ( 101 ) may be operatively connected to a single NIC ( 102 ), packet destinations (not shown) executing on the virtual machines ( 105 ,  110 ) of the host ( 101 ) operate as if the host ( 101 ) is bound to multiple NICs. In one or more embodiments of the invention, each of the virtual NICs ( 120 ,  125 ) is implemented in the MAC layer of the host ( 101 ). 
         [0022]    In one embodiment of the invention, each of the virtual NICs ( 120 ,  125 ) is operatively connected to a virtual machine ( 105 ,  110 ), where each virtual machine ( 105 ,  110 ) includes one or more virtual stacks ( 106 ,  111 ). In one embodiment of the invention, each virtual stack ( 106 ,  111 ) includes network layer functionality. In one embodiment of the invention, network layer functionality corresponds to functionality to manage packet addressing and delivery on a network (e.g., functionality to support IP, Address Resolution Protocol (ARP), Internet Control Message Protocol, etc.). In one embodiment of the invention, each virtual stack ( 106 ,  111 ) is configured to send and/or receive packets from one or more associated packet destinations (not shown) on the virtual machine ( 105 ,  110 ). Further, each virtual stack ( 106 ,  111 ) is configured to send and/or receive packets from an associated virtual NIC ( 120 ,  125 ). Further still, each virtual stack ( 106 ,  111 ) may also include functionality, as needed, to perform additional processing on the incoming and outgoing packets. This additional processing may include, but is not limited to, cryptographic processing, firewall routing, etc. In one embodiment of the invention, each of the virtual machines ( 105 ,  110 ) is located outside of the MAC layer (not shown) of the host ( 101 ). 
         [0023]    In one embodiment of the invention, each virtual machine ( 105 ,  110 ) shares host resources (e.g., one or more central processing units (CPU), memory, etc.) (not shown) with other virtual machines ( 105 ,  110 ) on the host ( 101 ). As discussed above, a virtual machine ( 105 ,  110 ) on a host ( 101 ) may include one or more packet destinations (e.g., containers and/or services) (not shown). In one embodiment of the invention, the packet destination(s) (e.g., containers and/or services) corresponds to any process or group of processes executing on the virtual machine of the host that sends and receives network traffic. Examples of packet destinations include, but are not limited to containers, services (e.g., web server), etc. 
         [0024]      FIG. 2  shows a flowchart in accordance with one embodiment of the invention. Initially, a virtual stack is created and bound to a packet destination executing on a virtual machine (STEP  210 ). Those skilled in the art will appreciate that the packet destination may be bound to the virtual stack anytime after the virtual stack has been created. In STEP  220 , a virtual NIC is created and bound to the virtual machine. At this stage, a software receive ring is created (STEP  230 ) and bound to both the virtual machine and a hardware receive ring (STEP  240 ). The classifier is subsequently programmed such that network traffic for the virtual machine is directed to the hardware ring bounded to the software ring created in STEP  230  (STEP  250 ). The software receive ring is then programmed to enforce bandwidth control (STEP  260 ). 
         [0025]    In one embodiment of the invention, programming the software ring to enforce bandwidth control (STEP  260 ) includes specifying a packet arrival rate threshold. In one embodiment of the invention, the packet arrival rate threshold specifies the maximum number of packets that may flow to the software ring over a given time interval (e.g., the maximum number of packets that may flow to the virtual NIC per second). Alternatively, the packet arrival rate threshold may specify the number of bytes of data that may flow to the software receive ring over a specific time interval. 
         [0026]    Those skilled in the art will appreciate that the steps shown in  FIG. 2  may be repeated as required to create any number of virtual stacks. Once the virtual network stack(s) has been created, as described above, the host may proceed to receive packets from the network. Those skilled in the art will also appreciate that the number of virtual stacks created using the steps shown in  FIG. 2  may vary based on the available system resources (e.g., number of CPUs, type of NIC, etc.). 
         [0027]      FIG. 3  shows a flowchart in accordance with one embodiment of the invention. Initially, a packet is received by the NIC (STEP  310 ). The classifier analyses the packet and determines to which of the hardware receive rings the packed should be sent. The packet is subsequently sent to the appropriate hardware receive ring (STEP  320 ). At this stage, the process determines the operating mode of the hardware receive ring (STEP  330 ). 
         [0028]    In one embodiment of the invention, a hardware receive ring may operate in polling mode. If the hardware receive ring is operating in polling mode, then the packet remains in the hardware receive ring until the software receive ring requests one or more packets from the hardware receive ring (STEP  340 ). In one embodiment of the invention, the software receive ring may request all packets in the hardware receive ring, or may request any number of packets in the hardware receive ring. Subsequently, the packet(s) is sent to the software receive ring (STEP  350 ). In one embodiment of the invention, the software ring may not request any packets if the packet arrival rate exceeds the packet arrival rate threshold. In one embodiment of the invention, the software ring may poll the hardware receive ring to keep the packet arrival rate at or below the packet arrival rate threshold. 
         [0029]    In one embodiment of the invention, the hardware receive ring may operate in interrupt mode. If the hardware receive ring is operating in interrupt mode, then the hardware receive ring may issue an interrupt when it receives the packet (STEP  360 ). The packet (and any additional packets at the time the interrupt is issued) on the hardware receive ring is then send to software receive ring (STEP  350 ). 
         [0030]    In STEP  370 , the packet(s) in the software receive ring is sent to virtual stack through the associated virtual NIC. In STEP  375 , it is determined whether the operation mode of the receive ring needs to be changed. In one embodiment of the invention, if the packet arrival rate at the software receive ring exceeds the packet arrival rate threshold, the hardware receive rings may be placed in polling mode (STEP  380 ). In one embodiment of the invention, if the packet arrival rate at the software receive ring is below the packet arrival rate threshold, the hardware receive ring may be placed in interrupt mode (or no action may be taken with respect to changing the operating mode) (STEP  380 ). 
         [0031]    The invention may be implemented on virtually any type of computer regardless of the platform being used. For example, as shown in  FIG. 4 , a computer system ( 400 ) includes a processor ( 402 ), associated memory ( 404 ), a storage device ( 406 ), and numerous other elements and functionalities typical of today&#39;s computers (not shown). The computer ( 400 ) may also include input means, such as a keyboard ( 408 ) and a mouse ( 410 ), and output means, such as a monitor ( 412 ). The computer system ( 400 ) is connected to a local area network (LAN) or a wide area network (e.g., the Internet) (not shown) via a network interface connection (not shown). Those skilled in the art will appreciate that these input and output means may take other forms. 
         [0032]    Further, those skilled in the art will appreciate that one or more elements of the aforementioned computer system ( 400 ) may be located at a remote location and connected to the other elements over a network. Further, the invention may be implemented on a distributed system having a plurality of nodes, where each portion of the invention (e.g., VNIC, software receive ring, virtual stack, etc.) may be located on a different node within the distributed system. In one embodiment of the invention, the node corresponds to a computer system. Alternatively, the node may correspond to a processor with associated physical memory. The node may alternatively correspond to a processor with shared memory and/or resources. Further, software instructions to perform embodiments of the invention may be stored on a computer readable medium such as a compact disc (CD), a diskette, a tape, a file, or any other computer readable storage device. 
         [0033]    While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein. Accordingly, the scope of the invention should be limited only by the attached claims.