SYSTEMS AND METHODS FOR A PARA-VITUALIZED DRIVER IN A MULTI-CORE VIRTUAL PACKET ENGINE DEVICE

• US 20120033673A1
• Filed: 08/05/2011
• Published: 02/09/2012
• Est. Priority Date: 08/06/2010
• Status: Abandoned Application

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: GOEL, DEEPAK
• Application Number:
  US13/204,065
• Publication Number:
  US 20120033673A1
• Time in Patent Office: Days
• US Class Current: 370/400
• 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: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 49/70 Virtual switches
• CPC Class Codes: H04L 69/12 Protocol engines

Abstract

The present invention is directed towards methods and systems for communicating packets between network interface hardware of a multi-core device and a plurality of virtualized packet processors executed by one or more cores of the multi-core device. A first virtualization domain on the device may receive a packet via the network interface hardware. The first virtualization domain may comprise a privileged domain having access to the hardware. The system may communicate the packet to a queue for a virtualized packet processor from a plurality of virtualized packet processors and executing within a second virtualization domain on a core. The second virtualization domain may not have direct access to the network interface hardware. The packet processor may determine that the queue includes a difference between a number of packets read from and written to the queue. The packet processor may process the packet from the queue responsive to the determination.

Claims

1. A method for communicating packets between network interface hardware of a multi-core device and a plurality of virtualized packet processors executed by one or more cores of the multi-core device, the method comprising:

(a) receiving, by a first virtualization domain executing on a multi-core device, a packet via a network interface hardware of the multi-core device, the first virtualization domain comprising a privileged domain having direct access to the network interface hardware;

(b) communicating the packet to a queue for a virtualized packet processor from a plurality of virtualized packet processors and executing within a second virtualization domain on a core of the multi-core device, the second virtualization domain from a plurality of virtualization domains not having direct access to the network interface hardware;

(c) determining, by the virtualized packet processor, that the queue includes a difference between a number of packets read from the queue and a number of packets written to the queue; and

(d) processing, by the virtualized packet processor, the packet from the queue responsive to the determination.

2. The method of claim 1, further comprising executing a first portion of a driver in the first virtualization domain for receiving the packet from the network interface hardware, and executing a second portion of the driver in the second virtualization domain for receiving the packet from the queue.

3. The method of claim 1, further comprising establishing the queue in kernel memory space of the multi-core device accessible by the first virtualization domain and the second virtualization domain.

4. The method of claim 1, further comprising assigning each of the plurality of virtualized packet processors with a corresponding queue in kernel memory space of the multi-core device.

5. The method of claim 1, further comprising executing the virtualized packet processor in user memory space of the multi-core device.

6. The method of claim 1, further comprising generating, by the virtualized packet processor a system call or hypervisor call to transfer the packet from the queue to the second virtualization domain responsive to identifying a difference between the number of packets read from the queue and the number of packets written to the queue.

7. The method of claim 1, wherein (d) further comprises converting the packet from a first format in the queue to a second format for processing by the virtualized packet processor.

8. The method of claim 1, further comprising transferring a plurality of packets from the queue to a receive queue of the virtualized packet processor residing in user memory space.

9. The method of claim 1, further comprising sending, by the first virtualization domain, the packet into a shared queue residing in kernel space of the multi-core device, prior to communicating the packet to the queue of the virtualized packet processor.

10. The method of claim 1, further comprising communicating the packet from the queue in kernel memory space to a receive queue of the second virtualization domain in user memory space of the multi-core device.

11. A method for communicating packets between network interface hardware of a multi-core device and a plurality of virtualized packet processors executed by one or more cores of the multi-core device, the method comprising:

(a) buffering, by a virtualized packet processor executing within a first virtualization domain on a core of a multi-core device, a packet in a transmit queue of the first virtualization domain, the first virtualization domain from a plurality of virtualization domains not having direct access to a network interface hardware of the multi-core device;

(b) determining, by the virtualized packet processor, that the transmit queue has one or more packets to transmit;

(c) transmitting, responsive to the determination, the one or more packets from the transmit queue to a shared queue residing on kernel memory space of the multi-core device accessible by a second virtualization domain, the second virtualization domain comprising a privileged domain having direct access to the network interface hardware; and

(d) accessing, by the second virtualization domain, the one or more packets from the shared queue in response to a notification from the first virtualization domain, for transmission via the network interface hardware to a network.

12. The method of claim 11, further comprising executing a first portion of a driver in the first virtualization domain buffer the packet in the transmit queue, and executing a second portion of the driver in the second virtualization domain to access the packet from the shared queue.

13. The method of claim 11, wherein the shared queue resides in kernel space of a hypervisor providing the first and second virtualization domains.

14. The method of claim 11, further comprising establishing the shared queue in kernel space of the multi-core device accessible by the first virtualization domain.

15. The method of claim 11, further comprising generating, by the virtualized packet processor, a system call to initiate communication of the one or more packets on the transmit queue to the shared queue in kernel memory space responsive to the buffering of the one or more packets on the transmit queue.

16. The method of claim 11 further comprising generating, by the virtualized packet processor, a hypervisor call in kernel memory space to initiate communication of the one or more packets on the transmit queue to the shared queue in kernel memory space.

17. The method of claim 11, wherein (a) further comprises converting the packet from a first format associated with the virtualized packet processor to a second format prior to buffering the packet in the transmit queue.

18. A system for communicating packets between network interface hardware of a multi-core device and a plurality of virtualized packet processors executed by one or more cores of the multi-core device, the system comprising:

a first virtualization domain executing on a first core of a multi-core device, comprising a privileged domain having direct access to the network interface hardware of the multi-core device, receiving a packet via the network interface hardware, and communicating the received packet to a queue in kernel mode of the multi-core device; and

a second virtualization domain from a plurality of virtualization domains not having direct access to the network interface hardware, executing on a second core of the multi-core device and comprising a virtualized packet processor that accesses the packet from the queue responsive to a determination that the queue has a difference between a number of packets read from the queue and a number of packets written to the queue.

19. The system of claim 18, wherein the first virtualization domain further comprises a first portion of a driver for receiving the packet from the network interface hardware, and the second virtualization domain further comprises a second portion of the driver for receiving the packet from the queue.

20. The system of claim 18, wherein the second virtualization domain generates, responsive to the determination, a system call or hypervisor call in kernel memory space to access the packet on the queue.