Multi-destination DMA for packet broadcast

Through the hardware NIC, network packets are written directly to the memory locations of multiple service processes through DMA operations, solving the throughput problems caused by proxy processes to replicate packets and improving I/O efficiency.

CN119072986APending Publication Date: 2024-12-03F5 NETWORKS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034071.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-16
Filing Date
2023-03-15
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

When multiple service processes share a network interface controller (NIC), the proxy process becomes a system bottleneck, resulting in multiple replication of network packets, especially in multicast scenarios, resulting in reduced I/O throughput.

Method used

Through the hardware NIC, direct memory access (DMA) operation is used to write network packets to the memory area accessible by the service process, avoiding the proxy process copying the packets and writing the packets directly to the destination memory location.

Benefits of technology

It improves the I/O throughput of the server computer, reduces the replication operation of the proxy process, and improves the efficiency of network packet transmission, especially in multicast scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072986A_ABST
    Figure CN119072986A_ABST
Patent Text Reader

Abstract

Techniques related to broadcast packet direct memory access (DMA) operations are disclosed. When a network interface controller (NIC) connected to a host computer receives a broadcast packet, it may send requests for multiple destination buffers to a proxy process running on the host computer. In some embodiments, the request to the agent includes all or part of the data packet, or metadata about the data packet. In such an embodiment, an agent may use the requested content to identify a service that should receive a data packet. Alternatively, the NIC may identify the destination service and may send an identifier of the destination service to the proxy. The proxy may send a request for a memory buffer to the service, and may receive a memory location identifier in response. The proxy may send the identifier to the NIC, which may perform a plurality of DMA operations to write the broadcast data packet to the identified memory location.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application No. 17 / 696,201, filed on March 16, 2022, the entire contents of which are hereby incorporated by reference. Technical Field

[0003] The present technology relates generally to network traffic management, and more particularly to managing network traffic for multiple services running on a computing device. Background Art

[0004] Recently, servers have been extended to perform multiple services, such as multiple virtual servers running on shared hardware in a cloud computing environment. In some scenarios, multiple services can be isolated from each other using virtual machines and / or virtualized containers. Current network interface controller (NIC) devices appear to the system software as a single monolithic device. Such NIC devices can be managed by a single device driver that communicates with multiple services running on the server via a virtual NIC interface. Summary of the invention

[0005] In an example embodiment, a method implemented by a network traffic management system includes: receiving a network data packet at a hardware network interface controller (NIC) connected to a host computer; sending, by the hardware NIC, metadata about the network data packet to an agent process running on the host computer; receiving a response message from the agent process at the hardware NIC, the response message including a memory location identifier; and writing, by the hardware NIC, the network data packet to a memory location of the host computer associated with the memory location identifier, wherein the writing includes performing a direct memory access (DMA) operation.

[0006] In another example embodiment, a system includes one or more network traffic management modules, networking modules or server modules, a memory including programming instructions stored thereon, and one or more processors, wherein the one or more processors are configured to execute the stored programming instructions to: receive a network data packet at a hardware network interface controller (NIC) connected to a host computer; send metadata about the network data packet to an agent process running on the host computer by the hardware NIC; receive a response message from the agent process at the hardware NIC, the response message including a memory location identifier; and write the network data packet to a memory location of the host computer associated with the memory location identifier by the hardware NIC, wherein the writing includes performing a direct memory access (DMA) operation.

[0007] In another example embodiment, a non-transitory computer-readable medium has instructions stored thereon, the instructions comprising executable code, which when executed by one or more processors causes the processors to: receive a network data packet at a hardware network interface controller (NIC) connected to a host computer; send, by the hardware NIC, metadata about the network data packet to an agent process running on the host computer; receive a response message from the agent process at the hardware NIC, the response message comprising a memory location identifier; and write, by the hardware NIC, the network data packet to a memory location of the host computer associated with the memory location identifier, wherein the writing comprises performing a direct memory access (DMA) operation.

[0008] In another example embodiment, a network traffic management device includes a memory and one or more processors, the memory including programming instructions stored thereon, the one or more processors being configured to execute the stored programming instructions to: receive a network data packet at a hardware network interface controller (NIC) connected to a host computer; send metadata about the network data packet to an agent process running on the host computer by the hardware NIC; receive a response message from the agent process at the hardware NIC, the response message including a memory location identifier; and write the network data packet to a memory location of the host computer associated with the memory location identifier by the hardware NIC, wherein the writing includes performing a direct memory access (DMA) operation.

[0009] In another example embodiment, a method implemented by a network traffic management system includes: receiving, by an agent process running on a host computer, metadata about a network data packet, wherein the metadata about the network data packet is received from a hardware network interface controller (NIC) connected to the host computer; using the metadata by the agent process to identify a memory buffer of the host computer; sending, by the agent process, a direct memory access (DMA) write message to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receiving, by the agent process, a notification message from the hardware NIC, the notification message indicating that the hardware NIC has performed a DMA operation to write the network data packet to the memory buffer of the host computer.

[0010] In another example embodiment, a system includes one or more network traffic management modules, networking modules or server modules, a memory including programming instructions stored thereon, and one or more processors, wherein the one or more processors are configured to execute the stored programming instructions to: receive metadata about a network data packet by an agent process running on a host computer, wherein the metadata about the network data packet is received from a hardware network interface controller (NIC) connected to the host computer; use the metadata by the agent process to identify a memory buffer of the host computer; send a direct memory access (DMA) write message by the agent process to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receive a notification message by the agent process from the hardware NIC, wherein the notification message indicates that the hardware NIC has performed a DMA operation to write the network data packet to the memory buffer of the host computer.

[0011] In another example embodiment, a non-transitory computer-readable medium has instructions stored thereon, the instructions comprising executable code, which when executed by one or more processors causes the processors to: receive, by an agent process running on a host computer, metadata about a network packet, wherein the metadata about the network packet is received from a hardware network interface controller (NIC) connected to the host computer; identify, by the agent process, a memory buffer of the host computer using the metadata; send, by the agent process, a direct memory access (DMA) write message to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receive, by the agent process, a notification message from the hardware NIC, the notification message indicating that the hardware NIC has performed a DMA operation to write the network packet to the memory buffer of the host computer.

[0012] In another example embodiment, a network traffic management device includes a memory and one or more processors, the memory including programming instructions stored thereon, the one or more processors being configured to be capable of executing the stored programming instructions to: receive metadata about a network data packet by an agent process running on a host computer, wherein the metadata about the network data packet is received from a hardware network interface controller (NIC) connected to the host computer; use the metadata by the agent process to identify a memory buffer of the host computer; send a direct memory access (DMA) write message by the agent process to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receive a notification message by the agent process from the hardware NIC, the notification message indicating that the hardware NIC has performed a DMA operation to write the network data packet to the memory buffer of the host computer.

[0013] In another example embodiment, a method implemented by a network traffic management system includes: receiving a network broadcast data packet by a hardware network interface controller (NIC) connected to a host computer; sending a request by the hardware NIC to an agent process running on the host computer to identify multiple memory locations in the host computer that should receive the network broadcast data packet; receiving a response from the agent process by the hardware NIC, the response including multiple memory location identifiers associated with the multiple memory locations; and writing the network broadcast data packet to the multiple memory locations in the host computer associated with the multiple memory location identifiers by the hardware NIC, wherein the writing includes performing multiple direct memory access (DMA) operations.

[0014] In another example embodiment, a system includes one or more network traffic management modules, networking modules or server modules, a memory including programming instructions stored thereon, and one or more processors, wherein the one or more processors are configured to execute the stored programming instructions to: receive a network broadcast data packet by a hardware network interface controller (NIC) connected to a host computer; send a request by the hardware NIC to an agent process running on the host computer to identify multiple memory locations in the host computer that should receive the network broadcast data packet; receive a response from the agent process by the hardware NIC, the response including multiple memory location identifiers associated with the multiple memory locations; and write the network broadcast data packet to the multiple memory locations in the host computer associated with the multiple memory location identifiers by the hardware NIC, wherein the writing includes performing multiple direct memory access (DMA) operations.

[0015] In another example embodiment, a non-transitory computer-readable medium has instructions stored thereon, the instructions comprising executable code, which when executed by one or more processors causes the processors to: receive a network broadcast data packet by a hardware network interface controller (NIC) connected to a host computer; send a request by the hardware NIC to an agent process running on the host computer to identify a plurality of memory locations in the host computer that should receive the network broadcast data packet; receive a response by the hardware NIC from the agent process, the response comprising a plurality of memory location identifiers associated with the plurality of memory locations; and write, by the hardware NIC, the network broadcast data packet to the plurality of memory locations in the host computer associated with the plurality of memory location identifiers, wherein the writing comprises performing a plurality of direct memory access (DMA) operations.

[0016] In another example embodiment, a network traffic management device includes a memory and one or more processors, the memory including programming instructions stored thereon, the one or more processors being configured to be capable of executing the stored programming instructions to: receive a network broadcast data packet by a hardware network interface controller (NIC) connected to a host computer; send a request by the hardware NIC to an agent process running on the host computer to identify multiple memory locations in the host computer that should receive the network broadcast data packet; receive a response from the agent process by the hardware NIC, the response including multiple memory location identifiers associated with the multiple memory locations; and write the network broadcast data packet to the multiple memory locations in the host computer associated with the multiple memory location identifiers by the hardware NIC, wherein the writing includes performing multiple direct memory access (DMA) operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a flow chart of an example method for performing a network packet direct memory access (DMA) write operation based on network packet metadata.

[0018] Figure 2 is a block diagram of an example network traffic management device for performing network packet DMA operations.

[0019] Figure 3 is a flow chart of an example method for identifying a destination memory buffer for a network packet DMA write operation using network packet metadata.

[0020] Figure 4 is a flow diagram of an example method for processing outbound network packets by a proxy process.

[0021] Figure 5 is a flow chart of an example method for processing outbound network packets by a hardware network interface controller (NIC).

[0022] Figure 6 is a flow chart of an example method for processing multi-destination network broadcast packets using DMA operations.

[0023] Figure 7 is a system diagram of an example system for performing network packet DMA operations.

[0024] Figure 8 is a block diagram of an example client-server architecture including a network traffic management device configured to perform network packet DMA operations.

[0025] Fig. 9 is a block diagram of an example computing environment. DETAILED DESCRIPTION

[0026] In a scenario where multiple service processes are running on a server computer (such as a network traffic management device), the service processes must share access to a network interface controller (NIC) device of the server computer in order to communicate with other computing devices via a computer network. Various techniques can be used to manage this shared access to the NIC device. For example, a service process can be configured to interface with an agent process (such as a driver registered in the operating system of the server computer) that manages the service process's access to the NIC device. The agent process can expose a virtual NIC interface to the service process. From the perspective of the service process, the virtual NIC interface can appear as a dedicated connection to the NIC device. However, the agent process can be aware of all existing virtual NIC interfaces and can manage the overall network packet flow between the NIC device and the service process.

[0027] However, in some scenarios (such as scenarios involving a large amount of network communication involving service processes), the proxy process may become a bottleneck of the system because each network packet may have to be copied multiple times. For example, a given network packet may have to be copied once from the NIC onboard memory to a memory area of ​​the server computer accessible to the proxy process. After the proxy process determines the destination service of the network packet, it may have to copy the network packet again to another memory area accessible to the destination service. In multicast scenarios, this problem may be more serious because a given network packet may have to be copied multiple times to the memory areas of multiple service processes.

[0028] At least some of the techniques described herein can be used to solve these problems by enabling a NIC device to use direct memory access (DMA) operations to write network packets to and read network packets from a memory area accessible to a service process. For example, when a NIC device receives a network packet, the NIC device can send a request for a memory buffer to which the network packet should be written to the proxy process. The proxy process can determine the destination service process of the network packet and can send a request for a free memory buffer to a virtual NIC interface associated with the destination service process. The proxy process can receive a response from the virtual NIC interface, the response including a memory location identifier associated with a free memory buffer accessible to the destination service process. The proxy process can send a response including a memory location identifier to the NIC device. The NIC device can then perform a DMA operation to write the network packet to a memory location associated with the memory location identifier of the server computer. Therefore, in at least some cases, the proxy process can be prevented from copying the network packet to a memory area associated with the destination service process. In many cases, the DMA operation performed by the NIC device is faster than the copy operation performed by the proxy process running on the server computer. Therefore, in at least some cases, the I / O throughput of the server computer can be improved.

[0029] In some embodiments, the NIC device's request for a free memory buffer may include all or part of the network data packet. Alternatively, the request for a free memory buffer may include metadata about the network data packet instead of all or part of the network data packet. In such an embodiment, copying the network data packet from the NIC device memory to the memory area associated with the proxy process may also be avoided.

[0030] Outbound transmission scenarios can also be supported. For example, the proxy process can receive a notification from the virtual NIC interface of the service process, which indicates that the outbound network data packet is ready to be sent. The notification may include a memory location identifier associated with the memory buffer storing the outbound network data packet. The proxy process can send a message to the NIC device, which includes the memory location identifier and indicates a request for outbound transmission. The NIC device can perform a DMA operation to read the network data packet from the memory location associated with the memory location identifier of the server computer, and can send the outbound network data packet via a network connection. The NIC device can send a notification message to the proxy process after the station network data packet has been read. Then, the proxy process can send a notification to the virtual NIC interface of the service process. Then, the service process can release the memory buffer and / or make the memory buffer available for additional outbound network data packets. In at least some embodiments, the proxy process can periodically poll the virtual NIC interface of the service process to determine whether the outbound network data packet is ready to be sent. In response to such a polling operation, a notification that the outbound data packet is ready to be sent can be received.

[0031] Multicast scenarios may also be supported. For example, when a network packet is received, the NIC device may send a request for a destination memory location to the proxy process, as described above. However, the proxy process may determine that there are multiple service processes that should receive the network packet. In this scenario, the proxy process may send a request for a free memory buffer to the virtual NIC interface of each of the identified service processes. The proxy process may receive a memory location identifier from each of the identified service processes, and may send multiple memory location identifiers to the NIC device. Upon receiving the multiple memory location identifiers, the NIC device may perform multiple DMA operations to write the network packet to the multiple identified memory locations.

[0032] Broadcast scenarios can also be supported. For example, the NIC device can receive a network broadcast data packet via a network connection. It is possible that multiple (but possibly less than all) service processes running on a server computer should receive a network broadcast data packet. For example, multiple service processes running on a server computer may be part of the same virtual network. The NIC device can send a request to the proxy process to identify the service process that should receive the network broadcast data packet. The NIC device can receive a response including multiple memory location identifiers from the proxy process. The NIC device can perform multiple DMA operations to write the network data packet to multiple memory locations associated with multiple memory location identifiers. In some embodiments, the request to the proxy process may include all or part of the network broadcast data packet, or metadata about the network broadcast data packet. In such an embodiment, the proxy process can use the content of the request to identify the service process that should receive the network broadcast data packet. Alternatively, the NIC device can identify the service process that should receive the network broadcast data packet. For example, the NIC device may include a data structure that can be used to identify the service process that should receive the network broadcast data packet. In an embodiment in which the NIC device identifies the destination service process, the request from the NIC device may include a service identifier associated with the destination service process. Once the destination service process has been identified (by the proxy process or the NIC device), the proxy process may send a request for a free memory buffer to the virtual NIC interface of the identified service process. The proxy process may receive a memory location identifier for the free memory buffer from the virtual NIC interface, and may send a plurality of memory location identifiers to the NIC device. The NIC device may perform a plurality of DMA operations to write the network broadcast data packet to the memory location associated with the plurality of memory location identifiers. The NIC device may send a notification to the proxy process indicating that the DMA write operation for the broadcast data packet has been completed. The proxy process may then send a notification to each of the destination service processes.

[0033] Figure 1 1 is a flow chart of an example method 100 for performing a network packet direct memory access (DMA) write operation based on network packet metadata. Any of the example devices and systems described herein may be used to perform all or part of the example method 100. For example, Figure 2 The example network traffic management device 210 depicted in can be used to perform all or part of the example method 100.

[0034] Figure 2is a block diagram of an example network traffic management device 210 for performing network packet DMA operations. The example network traffic management device 210 includes one or more processors 215, a hardware network interface controller (NIC) 220, and a memory 230. The memory 230 may include programming instructions stored thereon that are executable by the one or more processors 215. The programming instructions stored in the memory 230 include instructions for an agent process 250 that can be used to perform direct memory access (DMA) operations as described herein. The memory 230 may also include a plurality of memory locations 261-265 in which data items (such as network packets) may be stored. In at least some embodiments, the plurality of memory locations 261-265 may be targeted by DMA operations of the hardware NIC 220. In at least some such embodiments, the plurality of memory locations 261-265 may be associated with a plurality of service processes 281-285 running on the network traffic management device 210. Optionally, the memory 230 may include instructions of an operating system kernel 240. The network traffic management device 210 may use reference Fig. 9 The computing environment described in more detail is implemented.

[0035] refer to Figure 1 At 110, a network data packet is received at a hardware network interface controller (NIC) connected to a host computer. For example, the network data packet may be received at a hardware NIC 220 of the network traffic management device 210. The network data packet may be a data packet that complies with one or more computer network communication standards (e.g., TCP, IP, UDP, etc.). The network data packet may be received via one or more communication network channels (e.g., one or more wired and / or wireless computer networks, etc.).

[0036] At 120, metadata about the network data packet is sent by the hardware NIC to the agent process running on the host computer. For example, the hardware NIC 220 can send metadata about the received network data packet to the agent process 250 running on the network traffic management device 210. The metadata about the network data packet can be generated based on the content of the network data packet (such as, the content of one or more headers of the network data packet). In a specific embodiment, the metadata about the network data packet can be based on the value of the destination header of the network data packet. For example, the hardware NIC 220 can determine a destination identifier, such as an identifier of a service process (e.g., 281, 285, etc.) that should receive the network data packet. Optionally, the hardware NIC may include one or more data structures that can be used to identify one or more destinations of the network data packet based on the content of the network data packet. For example, the hardware NIC 220 may include a service lookup data structure 290, which the hardware NIC can use to identify a service process in a plurality of service processes 281-285 running on the network traffic management device 210.

[0037] At 130, a response message is received from the agent process at the hardware NIC, the response message including the memory location identifier. For example, the network interface controller 220 may receive a response message from the agent process 250, the response message including an identifier associated with a memory location in the plurality of memory locations 261-265.

[0038] At 140, the hardware NIC writes the network data packet to a memory location of the host computer associated with the memory location identifier, wherein the writing includes performing a direct memory access (DMA) operation. For example, the hardware NIC 220 may write the network data packet to a memory location associated with the memory location identifier in a plurality of memory locations 261-265. The hardware NIC 220 may write the data packet to the identified memory location (e.g., 261) using a DMA write operation. For example, the hardware NIC 220 may be connected to the memory 230 via one or more DMA access channels (not shown). The network data packet may be written to the identified memory location using one or more such DMA access channels.

[0039] Alternatively, the hardware NIC may send a message to the proxy process indicating that the writing of the network data packet to the memory location of the host computer has been completed. For example, the hardware NIC 220 may send a message to the proxy process 250 indicating that the writing of the network data packet to the memory in the plurality of memory locations 261-265 has been completed. The notification message may include a data structure sent by the hardware NIC to the proxy process. This may include writing the data structure to a memory area accessible to the proxy process by the hardware NIC. Additionally or alternatively, receiving the notification message may include observing changes (such as changes to index values) to the data structure by the proxy process. For example, the proxy process may be configured to monitor the data structure in the shared memory area. The hardware NIC may make one or more changes to the data structure to indicate that the hardware NIC has performed a DMA operation to write the network data packet to the memory location of the host computer. Then, the proxy process may receive the notification message by observing the changes made by the hardware NIC to the data structure in the shared memory area.

[0040] In at least some embodiments, the response message from the proxy process may include multiple memory location identifiers. In such embodiments, writing a network data packet may include writing the network data packet to each of multiple memory locations associated with multiple memory location identifiers. Writing a network data packet to multiple memories may include performing multiple DMA operations. For example, the hardware NIC 220 may perform multiple DMA operations to write the network data packet to multiple memory locations in multiple memory locations 261-265. In a specific example, the hardware NIC 220 may determine that the response from the proxy process 250 includes a memory location identifier associated with memory location 261, and another memory location identifier associated with memory location 265. Then, the hardware NIC 220 may perform a first DMA operation to write the network data packet to memory location 261. Then, the hardware NIC may perform a second DMA operation to write the network data packet to memory location 265.

[0041] Figure 3 is a flow chart of an example method 300 for identifying a destination memory buffer for a network packet DMA write operation using network packet metadata. Any of the example devices and systems described herein may be used to perform all or part of the example method 300. For example, Figure 2 The network traffic management device 210 depicted in can be used to perform all or part of the example method 300.

[0042] At 305, metadata about the network packet is received by an agent process running on the host computer. The metadata about the network packet can be received from a hardware NIC connected to the host computer. For example, the agent process 250 running on the network traffic management device 210 can receive metadata about the network packet from the hardware NIC 220.

[0043] At 310, the memory buffer of the host computer is identified by the agent process using metadata about the network packet. For example, the agent process 250 can identify the memory buffer of the network traffic management device 210 using metadata about the network packet.

[0044] Metadata about a network packet may include an identifier associated with a service process running on a host computer. For example, a plurality of service processes 281-285 may run on a network traffic management device 210. Metadata about a network packet may include an identifier associated with one of a plurality of service processes 281-285. In such an embodiment, identifying a memory buffer of a host computer may include a request for a free memory buffer sent by an agent process to a virtual NIC interface associated with the service process. Then, a memory location identifier may be received by the agent process from the virtual NIC interface. For example, the network traffic management device 210 may include a plurality of virtual NIC interfaces 271-275 associated with a plurality of service processes 281-285. The agent process 250 may send a request for a free memory buffer to a virtual NIC interface in a plurality of virtual NIC interfaces 271-275, and the virtual NIC interface is associated with a service process identified by a service process identifier in a plurality of service processes 281-285. Then, the agent process 250 may receive a memory location identifier from the virtual NIC interface to which a request for a free memory buffer was sent. The memory location identifier may be associated with the starting memory location of the requested free memory buffer. In a specific example, the agent process 250 determines that the identifier in the metadata about the network packet is associated with the service process 281, and sends a request for a free memory buffer to the virtual NIC interface 271 associated with the service process 281. The agent process 250 then receives the memory location identifier of the memory location 261 from the virtual NIC interface 271. Optionally, the memory 230 may include a data structure 290 that can be used by the agent process 250 to identify a service process in the plurality of service processes 281-285 and / or a virtual NIC interface in the plurality of virtual NIC interfaces 271-275 using the metadata about the network packet. For example, the agent process 250 may use the service identifier included in the metadata to find the service process and / or the virtual NIC interface.

[0045] At 320, a DMA write message is sent by the agent process to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer. For example, the agent process 250 may send a memory location identifier associated with the starting memory location (e.g., 261) of the memory buffer to the hardware NIC 220.

[0046] At 340, a notification message is received by the agent process from the hardware NIC, the notification message indicating that the hardware NIC has performed a DMA operation to write a network data packet to a memory buffer of the host computer. For example, the agent process 250 may receive a notification message from the hardware NIC 220, the notification message indicating that the hardware NIC 220 has performed a DMA operation to write a network data packet to a memory buffer of the network traffic management device 210. In a specific example, the agent process 250 may send a DMA write message to the hardware NIC 220, the DMA write message including a memory location identifier of the memory location 251. Then, the agent process 250 receives a notification message from the hardware NIC 220, the notification message indicating that the hardware NIC 220 has performed a DMA operation to write a network data packet to a memory buffer starting at the memory location 261.

[0047] In an embodiment where the metadata about a network packet includes an identifier associated with a service process running on a host computer, a notification message may be sent by the proxy process to a virtual NIC interface associated with the service process, wherein the notification message indicates that the network packet has been written to a memory buffer using a DMA operation. For example, after receiving a notification message indicating that a network packet has been written to a memory buffer from hardware NIC 220, proxy process 250 may send another notification message to a virtual NIC interface (e.g., 271) associated with a service process (e.g., 281) identified in the metadata about the network packet. The notification message may indicate to the service process (e.g., 281) that the network packet has been written to the memory buffer. The service process (e.g., 281) may then read the network packet from the memory buffer, and in at least some cases, the memory buffer may be released to make it available for receiving additional network packets.

[0048] In different or further embodiments, metadata about network packets may include tenant identifiers. Such tenant identifiers may be used to uniquely identify entities (such as customers, organizations, groups, etc.) associated with multiple service processes running on a host computer. In such embodiments, multiple service processes associated with tenant identifiers running on a host computer may be identified. The proxy process may send multiple requests for free memory buffers to multiple service processes, and may receive multiple memory location identifiers from multiple service processes in response. Then, the proxy process may send multiple DMA write messages to the hardware NIC. For example, the proxy process 250 may identify multiple service processes (e.g., 281-285) associated with the tenant identifier included in the metadata about the network packet running on the network traffic management device 210. The proxy process 250 may send multiple requests for free memory buffers to multiple identified service processes. For example, the proxy process 250 may send a first request for free memory buffers to the virtual NIC interface 271 associated with the service process 281, and may also send a second request for free memory buffers to the virtual NIC interface 275 associated with the service process 285. The agent process 250 may then receive a plurality of memory locations (e.g., 261-265) from the plurality of service processes 281-285. For example, the agent process 250 may receive a first memory location identifier (e.g., 261) associated with a first free memory buffer from the virtual NIC interface 271, and may receive a second memory location identifier (e.g., 265) associated with a second free memory buffer from the virtual NIC interface 275.

[0049] The agent process 250 may then send a plurality of DMA write messages to the hardware NIC 220. For example, the agent process 250 may send a first DMA write message including a memory location identifier associated with the memory location 261 to the hardware NIC 220, and may send a second DMA write message including a memory location identifier associated with the memory location 265 to the hardware NIC 220. Upon receiving the plurality of DMA write messages, the hardware NIC 220 may perform a plurality of DMA operations to write the network data packets to the locations (e.g., 261 and 265) in the memory 230 associated with the plurality of memory location identifiers.

[0050] Figure 4 4 is a flow chart of an example method 400 for processing outbound network packets by a proxy process. Any of the example devices and systems described herein may be used to perform all or part of the example method 400. For example, Figure 2 The network traffic management device 210 depicted in can be used to perform all or part of the example method 400.

[0051] At 405, a notification message is received by the agent process from a service process running on a host computer, wherein the notification message includes a memory location identifier associated with a buffer including an outbound network packet. For example, the agent process 250 may receive a notification message from a service process 281 running on a network traffic management device 210. Such a notification message may be received via a virtual NIC interface 271 associated with the service process 281. In at least some embodiments, receiving a notification message may include periodically polling the service process to determine whether there are any outbound network packets available for transmission. In response to such a polling operation, a memory location identifier associated with a buffer including an outbound network packet may be received. For example, the agent process 250 may periodically poll the virtual NIC interface 271 associated with the service process 281 to determine whether there are any outbound network packets from the service process 281 waiting to be transmitted. Similarly, the agent process 250 may periodically poll the virtual NIC interface 275 associated with the service process 285 to determine whether there are any outbound network packets from the service process 285 waiting to be transmitted. The agent process 250 may perform such polling operations for each service process that may generate outbound network packets (eg, for each service with which the agent process 250 may communicate using a virtual NIC interface).

[0052] At 410, the agent process sends a DMA read message including the memory location identifier to the hardware NIC. For example, the agent process 250 may send a DMA read message including the memory location identifier to the hardware NIC 220.

[0053] Optionally, at 420, a notification message is received by the agent process, the notification message indicating that the hardware NIC has performed a DMA operation to read an outbound data packet from a memory buffer. For example, the agent process 250 may receive a notification message from the hardware NIC 220, the notification message indicating that the hardware NIC 220 has performed a DMA operation to read an outbound network data packet from a buffer.

[0054] The notification message may include a data structure sent by the hardware NIC to the agent process. This may include writing the data structure to a memory area accessible to the agent process by the hardware NIC. Additionally or alternatively, receiving the notification message may include observing changes to the data structure (such as changes to an index value) by the agent process. For example, the agent process may be configured to monitor a data structure in a shared memory area. The hardware NIC may make one or more changes to the data structure to indicate that the hardware NIC has performed a DMA operation to read outbound data packets from a memory buffer. The agent process may then receive the notification message by observing changes made to the data structure in the shared memory area by the hardware NIC.

[0055] Optionally, at 430, the proxy process sends another notification message to the service process, indicating that the outbound network data packet has been sent. For example, the proxy process 250 can send a notification message to the virtual NIC interface 271 associated with the service process 281, indicating that the outbound network data packet has been sent.

[0056] The notification message may include a data structure sent by the proxy process to the service process. This may include writing the data structure to a memory area accessible to the service process (and / or the virtual NIC interface of the service process) by the proxy process. Additionally or alternatively, receiving the notification message may include observing changes to the data structure (such as changes to an index value) by the service process. For example, the service process (and / or the virtual NIC interface of the service process) may be configured to monitor a data structure in a shared memory area. The proxy process may make one or more changes to the data structure to indicate that an outbound data packet has been read from a memory buffer. The service process may then receive the notification message by observing changes made to the data structure in the shared memory area by the proxy process.

[0057] In a specific example, the agent process 250 polls the virtual NIC interface 271 of the service process 281 and receives a response indicating that an outbound network data packet is available in a memory buffer starting at the memory location 261. Such polling may include observing changes to a data structure in a shared memory area, which indicates that an outbound network data packet is present in the memory buffer starting at the memory location 261. The agent process 250 sends a DMA read message including a memory location identifier associated with the memory location 261 to the hardware NIC 220. The agent process 250 receives a notification message from the hardware NIC 220 indicating that an outbound network data packet has been read from the memory location 261. Receiving the notification message from the hardware NIC 220 may include observing changes to the data structure in the shared memory area by the agent process 250. Then, the agent process 250 sends a notification message to the virtual NIC interface 271 of the service process 281 indicating that the outbound network data packet has been sent. Sending the notification message to the virtual NIC interface 271 may include sending the data structure via the interface 271. Additionally or alternatively, sending the notification message may include making changes to a data structure in the shared memory area.Then, service process 281 may release the buffer beginning at memory location 261 and / or make the buffer beginning at memory location 261 available for storing additional outbound network packets.

[0058] Figure 5is a flow chart of an example method 500 for processing outbound network packets by a hardware NIC. Any of the example devices and systems described herein may be used to perform all or part of the example method 500. For example, Figure 2 The network traffic management device 210 depicted in FIG. 5 may be used to perform all or part of the example method 500 .

[0059] At 505, a send action message is received at the hardware NIC from an agent process running on a host computer connected to the hardware NIC. The send action message may include a memory location identifier associated with a send buffer of the host computer. For example, the hardware NIC 220 may receive a send action message from the agent process 250, the send action message including a memory location identifier associated with a first memory location (e.g., 261) of the send buffer.

[0060] At 510, the outbound network data packet is read from the send buffer by the hardware NIC, where the reading includes performing a DMA operation. For example, the hardware NIC 220 may perform a DMA operation to read the outbound network data packet from the send buffer starting at memory location 261. The hardware NIC 220 may then send the outbound network data packet via one or more computer networks to which the hardware NIC 220 is connected.

[0061] Optionally, at 520, the hardware NIC may send a notification message to the agent process indicating that the outbound network data packet has been read from the send buffer. For example, the hardware NIC 220 may send a notification message to the agent process 250 indicating that the outbound network data packet has been read from the memory location 261.

[0062] Figure 6 6 is a flow chart of an example method 600 for processing multi-destination network broadcast packets using DMA operations. Any of the example devices and systems described herein may be used to perform all or part of the example method 600. For example, Figure 2 The network traffic management device 210 depicted in FIG. 6 may be used to perform all or part of the example method 600. Additionally or alternatively, Figure 7 The depicted example system 700 may be used to perform all or part of the example method 600 .

[0063] Figure 77 is a system diagram of an example system 700 for performing network packet DMA operations. The example system 700 includes multiple service processes 711-715, an agent process 740, and a hardware NIC 760. In at least some embodiments, multiple service processes 711-715 and the agent process 740 can be run on a single host computer connected to the hardware NIC 760. However, other configurations are possible. Multiple service processes 711-715 are associated with multiple virtual NIC interfaces 731-735. The agent process 740 is configured to communicate with multiple virtual NIC interfaces 731-735. Multiple service processes 711-715 can be associated with multiple memory buffers 721-725. Multiple memory buffers 721-725 can be used to store network packets generated by multiple service processes 711-715, as well as network packets sent to multiple service processes 711-715. Figure 7 A single memory buffer is depicted as being associated with each service process. However, it is possible for a service process to be associated with multiple memory buffers.

[0064] refer to Figure 6 , at 605, a network broadcast data packet is received by a hardware NIC connected to a host computer. The network broadcast data packet can be received from another computing device connected to the host computer via a computer network. Alternatively, the network broadcast data packet can be received from a service process running on the host computer. For example, a network broadcast data packet 751 can be received by a hardware NIC 760. A network broadcast data packet can be a data packet sent to more than one destination. For example, a broadcast data packet can be a data packet intended to be sent to all receivers connected to a specified computer network (or a specified subnetwork). Additionally or alternatively, a broadcast data packet can be based on a destination lookup failure (DLF) of a unicast data packet. In at least some embodiments, the destination address of the broadcast data packet can include a special value indicating that it is a broadcast data packet. For example, an IP broadcast data packet can have a destination IP address header value of all 1s (e.g., 255.255.255.255).

[0065] At 610, a request is sent by the hardware NIC to the agent process running on the host computer to identify multiple memory locations in the host computer that should receive the network broadcast data packet. For example, the hardware NIC 760 can send a request 753 to the agent process 740 to identify multiple memory locations (e.g., buffers 721 and 723) that should receive the network broadcast data packet 751.

[0066] At 620, a response is received by the hardware NIC from the agent process, the response including a plurality of memory location identifiers associated with a plurality of memory locations in the host computer that should receive the network broadcast packet. For example, the hardware NIC 760 may receive a response 759 including a plurality of memory location identifiers associated with a plurality of memory locations (e.g., 721 and 723) that should receive the network broadcast packet 751. Although the response 759 is Figure 7 751, but in at least some embodiments, the response may include multiple messages. For example, the agent process 740 may send multiple messages, each of which includes one of the multiple memory location identifiers. In such an embodiment, the agent process 740 may send a special message (not shown) indicating that all memory location identifiers of the network broadcast data packet 751 have been sent.

[0067] At 630, the network broadcast data packet is written by the hardware NIC to a plurality of memory locations associated with the plurality of memory location identifiers, wherein the writing includes performing a plurality of DMA operations. For example, the hardware NIC 760 performs a plurality of DMA operations (e.g., 761 and 763) to write the network broadcast data packet 751 to a plurality of memory locations (e.g., 721 and 723) associated with the plurality of memory location identifiers included in the response 759.

[0068] In at least some embodiments, the proxy process can identify multiple service processes based on the content of the request received by the hardware NIC. Then, the proxy process can send multiple requests to multiple virtual NIC interfaces associated with the multiple service processes. The proxy process receives multiple responses from the multiple virtual NIC interfaces, wherein the multiple responses include multiple memory location identifiers. Multiple memory location identifiers can be identifiers of memory buffers, in which multiple service processes can read the network broadcast data packets after being written by the hardware NIC. For example, the proxy process 740 can identify multiple service processes (e.g., 711 and 713) that should receive the network broadcast data packet 751 based on the content of the request 753. The proxy process 740 can send multiple requests (e.g., 755 and 757) to free memory buffers (e.g., 721 and 723) to multiple virtual NIC interfaces (e.g., 731 and 733) associated with the identified multiple service processes (e.g., 711 and 713). The proxy process 740 may receive multiple responses (e.g., 756 and 758) from multiple virtual NIC interfaces (e.g., 731 and 733) to which requests for free memory buffers were sent. The multiple responses (e.g., 756 and 758) may include memory locations associated with free memory buffers for corresponding service processes (e.g., 711 and 713). The proxy process may generate multiple DMA descriptors (not shown) using multiple memory location identifiers (e.g., 756 and 758). The hardware NIC 760 may use the DMA descriptors to perform DMA write operations targeting memory locations (e.g., 721 and 723) associated with the memory location identifiers in the DMA descriptors. The multiple DMA descriptors may be included in the response 759 to the hardware NIC 760.

[0069] In at least one embodiment, the request to identify multiple memory locations includes all or part of the network broadcast packet. For example, request 753 may include all or part of network broadcast packet 751. In such an embodiment, proxy process 740 may identify multiple service processes (e.g., 711 and 713) that should receive network broadcast packet 751 based on the content of network broadcast packet 751.

[0070] Optionally, the proxy process can use the data structure to identify the service process that should receive the network broadcast data packet based on the content of the network broadcast data packet. For example, the proxy process 740 can use the content of the network broadcast data packet 751 to identify the service process that should receive the network broadcast data packet in the search data structure 780. The proxy process 740 can update the content of the data structure 780 based on the interaction between the proxy process 740 and multiple virtual NIC interfaces 731-735. For example, the virtual NIC interface (e.g., 731) can be registered with the proxy process 740. The registration may include the service identifier of the associated service process (e.g., 711), the tenant identifier of the tenant associated with the service process, and / or one or more virtual network identifiers. The proxy process 740 can update the data structure 780 to associate the virtual NIC interface (e.g., 731) with one or more virtual networks and / or the tenant identifier included.

[0071] In different or further embodiments, the request to identify multiple memories includes metadata about the network broadcast packet. For example, request 753 may include metadata about network broadcast packet 751. Such metadata may include a tenant identifier or be associated with the network broadcast packet. For example, hardware NIC 760 may identify a tenant associated with network broadcast packet 751 based on the content of network broadcast packet 751. In a specific example, hardware NIC 760 may identify a tenant associated with a source identifier (such as a source IP address) of network broadcast packet 751.

[0072] The proxy process 740 can identify multiple service processes (e.g., 711 and 713) based on the metadata in the request 753. In an embodiment where the metadata includes a tenant identifier, the proxy process 740 can identify multiple service processes (e.g., 711 and 713) associated with the tenant identifier. In a specific embodiment, the proxy process 740 identifies multiple service processes that are part of a virtual network associated with the tenant identifier included in the request 753.

[0073] Optionally, the proxy process can use the data structure to identify the service process that should receive the network broadcast data packet based on the metadata about the network broadcast data packet. For example, the proxy process 740 can use the metadata about the network broadcast data packet 751 to identify the service process that should receive the network broadcast data packet in the search data structure 780. The proxy process 740 can update the content of the data structure 780 based on the interaction between the proxy process 740 and multiple virtual NIC interfaces 731-735. For example, the virtual NIC interface (e.g., 731) can register with the proxy process 740. The registration may include the service identifier of the associated service process (e.g., 711) and / or the tenant identifier of the tenant associated with the service process. The proxy process 740 can update the data structure 780 to associate the virtual NIC interface (e.g., 731) with one or more virtual networks and / or the tenant identifier included.

[0074] In at least some embodiments, the hardware NIC can identify multiple service processes running on the host computer that should receive the network broadcast data packet based on the content of the network broadcast data packet. In such an embodiment, the request to identify multiple memories can include multiple service identifiers associated with multiple service processes. For example, the hardware NIC 760 can identify multiple services (e.g., 711 and 713) that should receive the network broadcast data packet 751 based on the content of the network broadcast data packet 751. For example, the hardware NIC 760 can determine the tenant identifier associated with the network broadcast data packet 751, and then can identify multiple service processes (e.g., 711 and 713) associated with the tenant identifier. In such an embodiment, the request 753 can include identifiers associated with multiple service processes.

[0075] Alternatively, the hardware NIC may use a data structure to identify a service process that should receive a network broadcast packet based on the content of a network broadcast packet. For example, the hardware NIC 760 may use the content of a network broadcast packet 751 to identify a service process that should receive a network broadcast packet 751 in a search data structure 780. The search data structure may be stored in the memory of the hardware NIC 760. The proxy process 740 may update the content of the data structure 780 based on the interaction between the proxy process 740 and a plurality of virtual NIC interfaces 731-735. For example, a virtual NIC interface (e.g., 731) may register with the proxy process 740. The registration may include a service identifier of an associated service process (e.g., 711), a tenant identifier of a tenant associated with the service process, and / or one or more virtual network identifiers. The proxy process 740 may update the content of the data structure 780 in the memory of the hardware NIC 760 to associate a service (e.g., 711) with one or more virtual networks and / or tenant identifiers. Thus, as service processes register and / or unregister with the agent process 740, the agent process 740 may make changes to the data structure 780 stored in the onboard memory of the hardware NIC 760 to reflect these changes.

[0076] In at least some embodiments, the response from the proxy process includes multiple DMA descriptors including multiple memory location identifiers. For example, the response 759 may include multiple DMA descriptors including multiple memory location identifiers associated with the memory locations (e.g., 721 and 723) to which the network broadcast data packet 751 should be written. The proxy process 740 may generate multiple DMA descriptors and send them to the hardware NIC 760 in the response 759. The hardware NIC may use the DMA descriptors to perform multiple DMA operations (e.g., 761 and 763).

[0077] Figure 8An example client-server architecture 800 (also referred to as a network traffic management system) incorporating a network traffic management device 810 is shown. The client-server architecture 800 includes a network traffic management device 810 that is coupled to one or more client computers (such as client computing devices 830A-N) via one or more communication networks (such as a communication network 840). Service processes 880A-N can communicate with the client computing devices 830A-N and / or one or more additional server computers (not shown) that can be accessed via the communication network 840 through an agent process 860 and a network interface controller (NIC) 850. As an example, the communication network 840A can include a public network (e.g., the Internet) and devices attached to the network 840 that can be accessed using a public network address. Additionally or alternatively, the communication network 840 can include a private network and devices attached to the network 840 that can be accessed using a private network address. Although Figure 8 A single network traffic management device 810 is depicted in FIG, but multiple network traffic management devices running additional service processes may be connected to the communication network 840. For example, multiple network traffic management devices (such as 810) may be connected to the communication network 840 and configured to function as a cloud computing environment.

[0078] The communication network 840 may include various wired and / or wireless communication technologies, such as a local area network (LAN), a wide area network (WAN), an intranet, the Internet, a public switched telephone network (PSTN), and the like. Devices connected to the communication network 840 may communicate with each other using various communication protocols, such as the Transmission Control Protocol and Internet Protocol (TCP / IP) over Ethernet and / or other custom or industry standard protocols. The communication protocol may be used to send information over the network 840 using packet-based messages (e.g., Ethernet-based packet data networks) and / or other application programming interfaces (APIs). An API is a programming interface (e.g., a set of methods and / or protocols) for communicating between different modules. The communication network 840 may include various network devices, such as, for example, switches (multi-layer or single-layer), routers, repeaters, gateways, bridges, hubs, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, modems, line drivers, and wireless access points. It should be noted that Figure 8 The network topology shown in has been simplified and multiple networks and networking devices can be utilized to interconnect the various computing systems disclosed herein. In addition, in these examples, one or more of the devices of the client-server architecture 800 can be in the same or different communication networks, including, for example, one or more public networks, private networks, or cloud networks.

[0079] Generally, the service processes 880A-N, the client devices 830A-N, and the network traffic management system 800 can execute commands using a computing environment such as Fig. 9 The computing environment may include computer hardware, computer software, and combinations thereof. As a specific example, a computing environment may include a general-purpose and / or special-purpose processor, a configurable and / or hard-wired electronic circuit, a communication interface, and a computer-readable memory for storing computer-executable instructions so that the processor can perform a given computing task. The logic for performing a given task may be specified in a single module or may be spread across multiple modules. As used herein, the terms "module" and "component" may refer to an implementation within one or more dedicated hardware devices or equipment (e.g., a computer), and / or an implementation within software hosted by one or more hardware devices or equipment that may host one or more other software applications or implementations.

[0080] The client devices 830A-N may include any type of computing device that can exchange network data, such as a mobile communication device, a laptop computer, a desktop computer, a tablet computer, a virtual machine executed within a cloud-based computer environment, and the like. The client devices 830A-N may run an interface application, such as a web browser or a standalone client application, which may provide an interface to communicate with one or more of the service processes 880A-N via the communication network 840 (e.g., request and receive content stored on the one or more service processes). The client devices 830A-N may also include an output device, such as a display screen or a touch screen (not shown), and / or an input device, such as a keyboard (not shown). In addition, one or more of the client devices 830A-N may be configured to execute software code (e.g., JavaScript code within a web browser) to record client-side data and provide the recorded data to the network traffic management device 810.

[0081] The network traffic management device 810 includes a NIC 850, an agent process 860, and a plurality of service processes 880A-N. The agent process can communicate with the plurality of service processes 880A-N via a plurality of virtual NIC interfaces 871-875. The service processes 880A-N can communicate with computing devices (e.g., client computing devices 830A-N) connected to the communication network 840 by exchanging network packets using the plurality of virtual NIC interfaces 871-875, the agent process 860, and the NIC 850 as described herein.

[0082] For example, the service processes 880A-N can exchange network data with the client devices 830A-N and with each other. As another example, the service processes 880A-N can exchange communications along the communication paths specified by the application logic to facilitate the client-server application to interact with the client devices 830A-N. Examples of the service processes 880A-N may include application services, database services, access control services, web services, and encryption services. Therefore, in some examples, one or more of the service processes 880A-N handle logins and other requests received from the client devices 830A-N according to the hypertext transfer protocol (HTTP) or hypertext transfer protocol secure (HTTPS) application layer protocol via the communication network 840. The web application can run as part of one or more of the service processes 880A-N and send data (e.g., files or web pages) to the client devices 830A-N in response to requests from the client devices 830A-N. The service processes 880A-N can represent a system with multiple servers in a pool that can include an internal or external network.

[0083] The service processes 880A-N are not limited to a particular configuration. Thus, the service processes 880A-N may operate using a coordination method whereby one of the service processes 880A-N operates to manage or otherwise coordinate the operation of the other service processes. Each of the service processes 880A-N may operate within resources within, for example, a cluster architecture, a peer-to-peer architecture, a virtual machine, or a cloud-based computer architecture. Therefore, the technology disclosed herein should not be construed as being limited to a single environment, and other configurations and architectures are also contemplated.

[0084] The network traffic management device 810 can perform a variety of functions, including, for example, providing network security, access control, load balancing network traffic on the service processes 880A-N, and / or accelerating network traffic associated with applications hosted by one or more of the service processes 880A-N. These functions can be performed by one or more of the service processes 880A-N or one or more other components of the network traffic management device 810. One or more of the service processes 880A-N can be incorporated into the workload performed by the network traffic management device 810. For example, the network traffic management device 810 can include a workload for performing proxy and other services on behalf of one or more of the service processes 880A-N and managing traffic between the clients 830A-N and the service processes 880A-N. In addition, the network traffic management device 810 can include other network devices, such as, for example, one or more routers or switches.

[0085] Although the network traffic management device 810 is shown in this example as including a single device, in other examples the network traffic management device 810 may include multiple devices or blades, each device or blade having one or more processors (each processor having one or more processing cores) that implement one or more components of the present technology. In these examples, one or more of the devices may have a dedicated communication interface or memory. Alternatively, one or more of the devices may utilize the memory, communication interface, or other hardware or software components of one or more other devices included in the network traffic management device 810. In addition, the network traffic management device 810 and / or the application executed by the network traffic management device 810 may operate in a cloud-based computing environment. The application may be executed in or as a virtual machine or virtual server that can be managed in a cloud-based computing environment. For example, the application and even the network traffic management device 810 itself may be located in a virtual server that runs in a cloud-based computing environment rather than being bound to one or more specific physical network computing devices. Moreover, the application may be run in one or more virtual machines (VMs) that are executed in one or more of the service processes 880A-N on the network traffic management device 810. Additionally, in one or more examples of the present technology, virtual machines running on the network traffic management device 810 can be managed or supervised by a hypervisor.

[0086] Fig. 9 A block diagram of a general example of a suitable computing environment 900 that can be used to implement the examples, techniques, or technologies described herein is shown. For example, the computing environment 900 can be used to implement a computing device (such as a network traffic management device) that performs network packet DMA operations as described herein.

[0087] The computing environment 900 includes at least one processing unit 910 and a computer readable memory 920, which are coupled together by an interconnect 930. The processing unit 910 executes computer executable instructions. The processing unit 910 may include a general-purpose processor, a special-purpose processor, and a combination thereof. For example, the processing unit 910 may include a general-purpose central processing unit (CPU), a graphics processor, a processor in an application-specific integrated circuit (ASIC), a processor configured to operate using programmable logic (such as in a field programmable gate array (FPGA)), and / or any other type of processor. In a multi-processing system, multiple processing units may be used to execute computer executable instructions to increase processing power.

[0088] The memory 920 stores software 940 that implements one or more innovations described herein in the form of computer executable instructions suitable for execution by the processing unit 910. Specifically, the memory 920 can be used to store computer executable instructions, data structures, input data, output data, and other information. The memory 920 may include volatile memory (e.g., registers, caches, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable ROM (EEPROM), and flash memory), and / or combinations thereof. The memory 920 may include operating system software (not shown). The operating system software may provide an operating environment for other software executed in the computing environment 900 and may coordinate the activities of the components of the computing environment 900.

[0089] The interconnect 930 is used to connect different components of the computing environment 900 together so that the processing unit 910 can communicate with the different components and / or so that the different components can communicate with each other. For example, the interconnect 930 may include a bus, a controller, and / or a network. As an example, the interconnect 930 may include a host bridge (also known as a north bridge) for connecting the processing unit 910 to relatively high-speed components (such as memory 920) and an input / output bridge (also known as a south bridge) for connecting the processing unit to relatively low-speed components (such as communication interface 950) within the computing environment 900. In some examples, one or more components of the computing environment 900 may be integrated into the processing unit 910 or directly connected to the processing unit.

[0090] The computing environment 900 may include a communication interface 950 for communicating with another computing entity using a communication medium (e.g., a physical layer). The communication interface 950 may implement all or part of a network protocol stack. The network protocol stack defines the communication format and rules for communicating between different devices connected to a network. For example, the network protocol stack may define modular layers for communication using the Open Systems Interconnection (OSI) model or another model (such as the Internet Protocol Suite). The OSI model standardizes and divides communication systems into seven layers, including a physical layer (referred to as layer 1) and an application layer (referred to as layer 7). The application layer may be used to define how applications access the communication subsystem. The physical layer defines the electrical and physical specifications for communicating through a communication medium (also referred to as a physical transmission medium). The communication medium may be used to transmit information, such as computer executable instructions or other data, in a modulated data signal. A modulated data signal is a signal in which one or more of its characteristics are adjusted in such a way as to encode information in the signal. The communication interface 950 may include electronic and / or optical circuitry to receive and send communication signals encoded using electrical, optical, radio frequency (RF), or another carrier signal (e.g., according to a physical layer specification of a network stack). Thus, the communication interface 950 may be used to communicate via wired connections (e.g., twisted pair, coaxial cable, and fiber optic connections) and / or wireless technologies (e.g., Bluetooth, WiFi (IEEE 802.11), and cellular). For reference Figure 8 In a specific example, the NIC 850 of the network traffic management device 610 can act as a communication interface that is operatively coupled to and communicates with the communication network 840.

[0091] The computing environment 900 may include a storage device 960 for storing instructions, data structures, and data of the software 940, which may be used to implement the techniques described herein. The storage device 960 may include electronic circuits for reading and / or writing to removable or non-removable storage media using a magnetic, optical, or other read and write system coupled to the processor. The storage device 960 may include a read-only storage medium and / or a readable and writable storage medium, such as a disk, a solid-state drive, a magnetic tape or cassette, a CD-ROM, a CD-RW, a DVD, or any other medium that may be used to store information and may be accessed within the computing environment 900.

[0092] The computing environment 900 may include an input device 970. For example, the input device 970 may provide an input interface with a user of the computing environment 900 and / or for receiving input from the physical environment. The input device 970 may include a tactile input device (e.g., a keyboard, mouse, or touch screen), a microphone, a camera, a sensor, or another device that provides input to the computing environment 900.

[0093] The computing environment 900 may include an output device 980. For example, the output device 980 may provide an output interface with a user of the computing environment 900 and / or for generating output observable in a physical environment. The output device 980 may include a light emitting diode, a display, a printer, a speaker, a CD writer, or another device that provides output from the computing environment 900. In some examples, the input device 970 and the output device 980 may be used together to provide a user interface to a user of the computing environment 900.

[0094] The computing environment 900 is not intended to limit the scope of use or functionality of the technology, because the technology can be implemented in different general and / or special computing environments. For example, the disclosed technology can be practiced in a local, distributed and / or network-supported computing environment. In a distributed computing environment, tasks are performed by multiple processing devices. Therefore, the principles and advantages of distributed processing, such as redundancy, parallelization and replication, can also be implemented as needed to improve the robustness and performance of the device and system of the example. The example can also be implemented on a computer system that extends across any suitable network using any suitable interface mechanism and traffic technology, and the network includes (only as an example) a wireless traffic network, a cellular traffic network, a packet data network (PDN), the Internet, an intranet and a combination thereof. As a specific example, a distributed computing environment may include a processing unit 910 and a network-accessible computing environment 990 linked by a communication network. In a distributed computing environment, program modules 940 (including executable instructions for performing operations as described herein) can be located in both local and remote memory storage devices.

[0095] The term computer-readable medium includes non-transitory media for data storage, such as memory 920 and storage device 960, and does not include transmission media such as modulated data signals and carrier waves. Any disclosed method can be implemented as a computer executable instruction stored on one or more computer-readable media and executed on a computer (e.g., any commercially available computer). Any computer executable instructions for implementing the disclosed technology and any data structures and data created and used during the implementation of the disclosed embodiment can be stored on one or more computer-readable storage media. For example, a computer executable instruction can be a part of a dedicated software application or a software application accessed or downloaded via a web browser or other software application (such as a remote computing application). For example, such software can be executed on a single local computer (e.g., any suitable commercially available computer) or in a network environment (e.g., via the Internet, a wide area network, a local area network, a client-server network or other such networks) using one or more network-attached computers.

[0096] 1. A method implemented by a network traffic management system, the method comprising: receiving a network data packet at a hardware network interface controller (NIC) connected to a host computer; sending, by the hardware NIC, metadata about the network data packet to an agent process running on the host computer; receiving a response message from the agent process at the hardware NIC, the response message including a memory location identifier; and writing, by the hardware NIC, the network data packet to a memory location of the host computer associated with the memory location identifier, wherein the writing comprises performing a direct memory access (DMA) operation.

[0097] 2. The method of claim 1 further comprising sending, by the hardware NIC, a message to the proxy process indicating that the writing of the network data packet to the memory location of the host computer has been completed.

[0098] 3. A method as claimed in claim 1, wherein: the response message includes multiple memory location identifiers, including the memory location identifier; and the writing of the network data packet includes writing the network data packet to each of a plurality of memory locations associated with the plurality of memory location identifiers, wherein the writing includes performing multiple DMA operations.

[0099] 4. The method of claim 1 further comprising: receiving a send action message from the agent process at the hardware NIC, wherein the send action message includes a memory location identifier associated with a send buffer of the host computer; and reading, by the hardware NIC, an outbound network packet from the send buffer, wherein the reading includes performing another DMA operation.

[0100] 5. The method of claim 1 , wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; and the method further comprises generating, by the hardware NIC, the identifier associated with the service process based on content of the network data packet.

[0101] 6. A system comprising one or more network traffic management modules, networking modules or server modules, a memory including programming instructions stored thereon, and one or more processors, wherein the one or more processors are configured to execute the stored programming instructions to: receive a network data packet at a hardware network interface controller (NIC) connected to a host computer; send metadata about the network data packet to an agent process running on the host computer by the hardware NIC; receive a response message from the agent process at the hardware NIC, the response message including a memory location identifier; and write the network data packet to a memory location of the host computer associated with the memory location identifier by the hardware NIC, wherein the writing includes performing a direct memory access (DMA) operation.

[0102] 7. The system of claim 6, wherein: the one or more processors are further configured to be capable of executing the stored programming instructions to: send a message by the hardware NIC to the proxy process, the message indicating that the writing of the network data packet to the memory location of the host computer has been completed.

[0103] 8. A system as claimed in claim 6, wherein: the response message includes multiple memory location identifiers, including the memory location identifier; and the writing of the network data packet includes writing the network data packet to each of a plurality of memory locations associated with the plurality of memory location identifiers, wherein the writing includes performing multiple DMA operations.

[0104] 9. The system of claim 6, wherein the one or more processors are further configured to be capable of executing the stored programming instructions to: receive a send action message from the agent process at the hardware NIC, wherein the send action message includes a memory location identifier associated with a send buffer of the host computer; and read, by the hardware NIC, an outbound network packet from the send buffer, wherein the reading includes performing another DMA operation.

[0105] 10. The system of claim 6, wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; and the one or more processors are further configured to be capable of executing stored programming instructions to generate, by the hardware NIC, the identifier associated with the service process based on the content of the network data packet.

[0106] 11. A non-transitory computer-readable medium having instructions stored thereon, the instructions comprising executable code, which, when executed by one or more processors, causes the processors to: receive a network data packet at a hardware network interface controller (NIC) connected to a host computer; send metadata about the network data packet to an agent process running on the host computer by the hardware NIC; receive a response message from the agent process at the hardware NIC, the response message comprising a memory location identifier; and write the network data packet to a memory location of the host computer associated with the memory location identifier by the hardware NIC, wherein the writing comprises performing a direct memory access (DMA) operation.

[0107] 12. The non-transitory computer-readable medium of claim 11, wherein: the instructions further comprise executable code which, when executed by one or more processors, causes the processors to: send a message by the hardware NIC to the proxy process, the message indicating that the writing of the network data packet to the memory location of the host computer has been completed.

[0108] 13. A non-transitory computer-readable medium as described in claim 11, wherein: the response message includes multiple memory location identifiers, including the memory location identifier; and the writing of the network data packet includes writing the network data packet to each of a plurality of memory locations associated with the plurality of memory location identifiers, wherein the writing includes performing multiple DMA operations.

[0109] 14. The non-transitory computer-readable medium of claim 11, wherein: the instructions further comprise executable code that, when executed by one or more processors, causes the processors to: receive a send action message from the agent process at the hardware NIC, wherein the send action message comprises a memory location identifier associated with a send buffer of the host computer; and read, by the hardware NIC, an outbound network packet from the send buffer, wherein the reading comprises performing another DMA operation.

[0110] 15. The non-transitory computer-readable medium of claim 11, wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; and the instruction further includes executable code that, when executed by one or more processors, causes the processor to generate, by the hardware NIC, the identifier associated with the service process based on the contents of the network data packet.

[0111] 16. A network traffic management device comprising a memory and one or more processors, the memory including programming instructions stored thereon, the one or more processors being configured to execute the stored programming instructions to: receive a network data packet at a hardware network interface controller (NIC) connected to a host computer; send metadata about the network data packet to an agent process running on the host computer by the hardware NIC; receive a response message from the agent process at the hardware NIC, the response message including a memory location identifier; and write the network data packet to a memory location of the host computer associated with the memory location identifier by the hardware NIC, wherein the writing includes performing a direct memory access (DMA) operation.

[0112] 17. A network traffic management device as described in claim 16, wherein: the one or more processors are also configured to be able to execute the stored programming instructions to: send a message from the hardware NIC to the agent process, indicating that the writing of the network data packet to the memory location of the host computer has been completed.

[0113] 18. A network traffic management device as described in claim 16, wherein: the response message includes multiple memory location identifiers, including the memory location identifier; and writing the network data packet includes writing the network data packet to each of a plurality of memory locations associated with the plurality of memory location identifiers, wherein the writing includes performing multiple DMA operations.

[0114] 19. A network traffic management device as described in claim 16, wherein: the one or more processors are also configured to be able to execute stored programming instructions to: receive a send action message from the agent process at the hardware NIC, wherein the send action message includes a memory location identifier associated with a send buffer of the host computer; and read an outbound network packet from the send buffer by the hardware NIC, wherein the reading includes performing another DMA operation.

[0115] 20. A network traffic management device as described in claim 16, wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; and the one or more processors are also configured to be able to execute stored programming instructions to generate the identifier associated with the service process by the hardware NIC based on the content of the network data packet.

[0116] 21. A method implemented by a network traffic management system, the method comprising: receiving metadata about a network data packet by an agent process running on a host computer, wherein the metadata about the network data packet is received from a hardware network interface controller (NIC) connected to the host computer; using the metadata by the agent process to identify a memory buffer of the host computer; sending a direct memory access (DMA) write message by the agent process to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receiving a notification message by the agent process from the hardware NIC, the notification message indicating that the hardware NIC has performed a DMA operation to write the network data packet to the memory buffer of the host computer.

[0117] 22. A method as claimed in claim 21, wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; the identifying the memory buffer of the host computer includes: the agent process sending a request for a free memory buffer to a virtual NIC interface associated with the service process, and the agent process receiving the memory location identifier from the virtual NIC interface; and the method also includes the agent process sending a notification message to the virtual NIC interface, wherein the notification message indicates that the network data packet has been written to the memory buffer.

[0118] 23. A method as claimed in claim 21, wherein: the metadata about the network data packet includes a tenant identifier; and the method further includes: identifying multiple service processes associated with the tenant identifier running on the host computer; sending multiple requests for free memory buffers to the multiple service processes; receiving multiple memory location identifiers from the multiple service processes by the agent process, including the memory location identifier; and sending multiple DMA write messages to the hardware NIC by the agent process, including the DMA write message.

[0119] 24. The method of claim 21 further comprises: receiving, by the agent process, a notification message from a service process running on the host computer, wherein the notification message comprises a memory location identifier associated with a buffer comprising an outbound network data packet; and sending, by the agent process, a DMA read message comprising the memory location identifier to the hardware NIC.

[0120] 25. The method as claimed in claim 24 also includes: receiving a notification message by the agent process, the notification message indicating that the hardware NIC has performed a DMA operation to read the outbound network data packet from the buffer; and sending another notification message by the agent process to the service process, the other notification message indicating that the outbound network data packet has been sent.

[0121] 26. A system comprising one or more network traffic management modules, networking modules or server modules, a memory including programming instructions stored thereon, and one or more processors, wherein the one or more processors are configured to execute the stored programming instructions to: receive metadata about a network data packet by an agent process running on a host computer, wherein the metadata about the network data packet is received from a hardware network interface controller (NIC) connected to the host computer; use the metadata by the agent process to identify a memory buffer of the host computer; send a direct memory access (DMA) write message by the agent process to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receive a notification message by the agent process from the hardware NIC, wherein the notification message indicates that the hardware NIC has performed a DMA operation to write the network data packet to the memory buffer of the host computer.

[0122] 27. A system as described in claim 26, wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; the identifying the memory buffer of the host computer includes: the agent process sending a request for a free memory buffer to a virtual NIC interface associated with the service process, and the agent process receiving the memory location identifier from the virtual NIC interface; and the one or more processors are also configured to be able to execute the stored programming instructions to send a notification message by the agent process to the virtual NIC interface, wherein the notification message indicates that the network data packet has been written to the memory buffer.

[0123] 28. A system as claimed in claim 26, wherein: the metadata about the network data packet includes a tenant identifier; and the one or more processors are also configured to be able to execute stored programming instructions to: identify multiple service processes associated with the tenant identifier running on the host computer; send multiple requests for free memory buffers to the multiple service processes; receive, by the agent process, multiple memory location identifiers from the multiple service processes, including the memory location identifier; and send, by the agent process, multiple DMA write messages to the hardware NIC, including the DMA write message.

[0124] 29. The system of claim 26, wherein the one or more processors are further configured to be capable of executing the stored programming instructions to: receive, by the agent process, a notification message from a service process running on the host computer, wherein the notification message includes a memory location identifier associated with a buffer including an outbound network data packet; and send, by the agent process, a DMA read message including the memory location identifier to the hardware NIC.

[0125] 30. A system as described in claim 29, wherein the one or more processors are further configured to be able to execute the stored programming instructions to: receive a notification message by the agent process, the notification message indicating that the hardware NIC has performed a DMA operation to read the outbound network data packet from the buffer; and send another notification message by the agent process to the service process, the other notification message indicating that the outbound network data packet has been sent.

[0126] 31. A non-transitory computer-readable medium having instructions stored thereon, the instructions comprising executable code, which when executed by one or more processors causes the processors to: receive metadata about a network packet by an agent process running on a host computer, wherein the metadata about the network packet is received from a hardware network interface controller (NIC) connected to the host computer; use the metadata by the agent process to identify a memory buffer of the host computer; send a direct memory access (DMA) write message by the agent process to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receive a notification message by the agent process from the hardware NIC, the notification message indicating that the hardware NIC has performed a DMA operation to write the network packet to the memory buffer of the host computer.

[0127] 32. A non-transitory computer-readable medium as described in claim 31, wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; the identifying the memory buffer of the host computer includes: sending a request for a free memory buffer by the agent process to a virtual NIC interface associated with the service process, and receiving the memory location identifier from the virtual NIC interface by the agent process; and the instructions also include executable code, which, when executed by one or more processors, causes the processor to send a notification message from the agent process to the virtual NIC interface, wherein the notification message indicates that the network data packet has been written to the memory buffer.

[0128] 33. A non-temporary computer-readable medium as described in claim 31, wherein: the metadata about the network data packet includes a tenant identifier; and the instructions also include executable code, which, when executed by one or more processors, causes the processor to: identify multiple service processes associated with the tenant identifier running on the host computer; send multiple requests for free memory buffers to the multiple service processes; receive, by the agent process, multiple memory location identifiers from the multiple service processes, including the memory location identifier; and send, by the agent process, multiple DMA write messages to the hardware NIC, including the DMA write message.

[0129] 34. A non-transitory computer-readable medium as described in claim 31, wherein: the instructions also include executable code, which, when executed by one or more processors, causes the processor to: receive, by the agent process, a notification message from a service process running on the host computer, wherein the notification message includes a memory location identifier associated with a buffer including an outbound network data packet; and send, by the agent process, a DMA read message including the memory location identifier to the hardware NIC.

[0130] 35. A non-transitory computer-readable medium as described in claim 34, wherein: the instructions also include executable code, which, when executed by one or more processors, causes the processor to: receive a notification message by the agent process, the notification message indicating that the hardware NIC has performed a DMA operation to read the outbound network data packet from the buffer; and send another notification message by the agent process to the service process, the other notification message indicating that the outbound network data packet has been sent.

[0131] 36. A network traffic management device comprising a memory and one or more processors, the memory including programming instructions stored thereon, the one or more processors being configured to be able to execute the stored programming instructions to: receive metadata about a network data packet by an agent process running on a host computer, wherein the metadata about the network data packet is received from a hardware network interface controller (NIC) connected to the host computer; use the metadata by the agent process to identify a memory buffer of the host computer; send a direct memory access (DMA) write message by the agent process to the hardware NIC, wherein the DMA write message includes a memory location identifier associated with the memory buffer; and receive a notification message by the agent process from the hardware NIC, the notification message indicating that the hardware NIC has performed a DMA operation to write the network data packet to the memory buffer of the host computer.

[0132] 37. A network traffic management device as described in claim 36, wherein: the metadata about the network data packet includes an identifier associated with a service process running on the host computer; the identifying the memory buffer of the host computer includes: the agent process sending a request for a free memory buffer to a virtual NIC interface associated with the service process, and the agent process receiving the memory location identifier from the virtual NIC interface; and the one or more processors are also configured to be able to execute stored programming instructions to send a notification message by the agent process to the virtual NIC interface, wherein the notification message indicates that the network data packet has been written to the memory buffer.

[0133] 38. A network traffic management device as described in claim 36, wherein: the metadata about the network data packet includes a tenant identifier; and the one or more processors are also configured to be able to execute stored programming instructions to: identify multiple service processes associated with the tenant identifier running on the host computer; send multiple requests for free memory buffers to the multiple service processes; receive, by the agent process, multiple memory location identifiers from the multiple service processes, including the memory location identifier; and send, by the agent process, multiple DMA write messages to the hardware NIC, including the DMA write message.

[0134] 39. A network traffic management device as described in claim 36, wherein the one or more processors are further configured to be capable of executing stored programming instructions to: receive, by the agent process, a notification message from a service process running on the host computer, wherein the notification message includes a memory location identifier associated with a buffer including outbound network data packets; and send, by the agent process, a DMA read message including the memory location identifier to the hardware NIC.

[0135] 40. A network traffic management device as described in claim 36, wherein the one or more processors are further configured to be able to execute the stored programming instructions to: receive a notification message by the agent process, the notification message indicating that the hardware NIC has performed a DMA operation to read the outbound network data packet from the buffer; and send another notification message by the agent process to the service process, the other notification message indicating that the outbound network data packet has been sent.

[0136] The present disclosure is set forth in the context of representative examples that are not intended to be limiting. Therefore, the present disclosure is directed to all novel and non-obvious features and aspects of the various disclosed examples, which are individual and various combinations and sub-combinations of each other. Many variations of the specific hardware and software used to implement the examples are possible, as will be understood by those skilled in the relevant art with the benefit of the present disclosure. The disclosed systems, methods, and devices are not limited to any particular aspect or feature or combination thereof, nor do the disclosed techniques require the presence of any one or more specific advantages or problem solving. The provision of theories of operation, scientific principles, or other theoretical descriptions proposed herein with reference to the disclosed techniques is for better explanation and is not intended to limit the scope. The devices and methods in the appended claims are not limited to those devices and methods that function in a manner described by such theories of operation.

[0137] As used in this application, the singular forms "a", "an" and "the" include the plural forms unless the context clearly indicates otherwise. The term "coupled" includes mechanical, electrical, magnetic, optical and other practical ways of coupling or linking items together, and does not exclude the presence of intermediate elements between the coupled items. The term "and / or" refers to any one item or combination of items in the phrase.

[0138] Therefore, the order of the listed processing elements or sequences, or the use of numbers, letters or other names, is not intended to limit the claimed process to any order. Although the operations of some disclosed methods are described in a specific, sequential order for ease of presentation, it should be understood that such descriptions include rearrangements unless the specific claim language set forth below requires a specific order. For example, the operations described in sequence may be rearranged or performed simultaneously in some cases. In addition, for simplicity, the accompanying drawings may not show all the various ways in which the disclosed methods can be used in combination with other methods.

[0139] It should also be fully understood that any software functionality described herein may be performed at least in part by one or more hardware logic components rather than software. For example, but not limited to, illustrative types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), and the like.

[0140] For the sake of clarity, only certain selected aspects of software-based implementations are described. Other details known in the art are omitted. For example, it should be understood that the disclosed technology is not limited to any particular computer language or program. For example, the disclosed technology can be implemented by software written in C, C++, Java, assembly language, or any other suitable programming language. Similarly, the disclosed technology is not limited to any particular computer or hardware type. Certain details of suitable computers and hardware are known and do not need to be elaborated in this disclosure.

[0141] Having thus described many possible embodiments to which the principles of the present invention may be applied, those skilled in the art will recognize that the foregoing detailed disclosure is intended to be presented by way of example only and is not restrictive. Although not expressly stated herein, various changes, improvements and modifications will occur and are intended to be used by those skilled in the art. These changes, improvements and modifications are intended to be proposed herein and are within the spirit and scope of the present invention. Therefore, the scope of the subject matter claimed is defined by the appended claims. We therefore claim that our invention falls entirely within the scope of these claims.

Claims

1. A method implemented by a network traffic management system, the method comprising: Network broadcast packets are received by a hardware network interface controller (NIC) connected to a host computer; Sending a request by the hardware NIC to an agent process running on the host computer to identify a plurality of memory locations in the host computer that should receive the network broadcast data packets; receiving, by the hardware NIC, a response from the agent process, the response comprising a plurality of memory location identifiers associated with the plurality of memory locations; as well as The network broadcast data packets are written, by the hardware NIC, to the plurality of memory locations in the host computer that are associated with the plurality of memory location identifiers, wherein the writing comprises performing a plurality of direct memory access (DMA) operations.

2. The method of claim 1, wherein: The response from the agent process includes a plurality of DMA descriptors including the plurality of memory location identifiers; as well as The method further comprises: The proxy process identifies a plurality of service processes based on the content of the request, sending, by the proxy process, a plurality of requests for available memory buffers to a plurality of virtual NIC interfaces associated with the plurality of service processes, receiving, by the agent process, a plurality of responses from the plurality of virtual NIC interfaces, wherein the plurality of responses include the plurality of memory location identifiers, and The plurality of DMA descriptors are generated by the agent process using the plurality of memory location identifiers.

3. The method of claim 2, wherein: The request identifying the plurality of memory locations comprises the network broadcast packet.

4. The method of claim 2, wherein: The request identifying the plurality of memory locations includes metadata about the network broadcast data packet.

5. The method of claim 1, wherein: The method further includes identifying, by the hardware NIC, a plurality of service processes that should receive the network broadcast data packet based on the content of the network broadcast data packet, wherein the plurality of service processes are running on the host computer; as well as The request identifying the plurality of memory locations includes a plurality of service identifiers associated with the plurality of service processes.

6. A system comprising one or more network traffic management modules, networking modules or server modules, a memory including programming instructions stored thereon, and one or more processors configured to execute the stored programming instructions to: Network broadcast packets are received by a hardware network interface controller (NIC) connected to a host computer; Sending a request by the hardware NIC to an agent process running on the host computer to identify a plurality of memory locations in the host computer that should receive the network broadcast data packets; receiving, by the hardware NIC, a response from the agent process, the response comprising a plurality of memory location identifiers associated with the plurality of memory locations; as well as The network broadcast data packets are written, by the hardware NIC, to the plurality of memory locations in the host computer that are associated with the plurality of memory location identifiers, wherein the writing comprises performing a plurality of direct memory access (DMA) operations.

7. The system of claim 6, wherein: The response from the agent process includes a plurality of DMA descriptors including the plurality of memory location identifiers; and The one or more processors are further configured to execute stored programming instructions to: The proxy process identifies a plurality of service processes based on the content of the request, sending, by the proxy process, a plurality of requests for available memory buffers to a plurality of virtual NIC interfaces associated with the plurality of service processes, receiving, by the agent process, a plurality of responses from the plurality of virtual NIC interfaces, wherein the plurality of responses include the plurality of memory location identifiers, and The plurality of DMA descriptors are generated by the agent process using the plurality of memory location identifiers.

8. The system of claim 7, wherein: The request identifying the plurality of memory locations comprises the network broadcast packet.

9. The system of claim 7, wherein: The request identifying the plurality of memory locations includes metadata about the network broadcast data packet.

10. The system of claim 6, wherein: The one or more processors are further configured to execute the stored programming instructions to identify, by the hardware NIC, a plurality of service processes that should receive the network broadcast data packet based on the content of the network broadcast data packet, wherein the plurality of service processes are running on the host computer; as well as The request identifying the plurality of memory locations includes a plurality of service identifiers associated with the plurality of service processes.

11. A non-transitory computer readable medium having stored thereon instructions, the instructions comprising executable code that, when executed by one or more processors, causes the processors to: Network broadcast packets are received by a hardware network interface controller (NIC) connected to a host computer; Sending a request by the hardware NIC to an agent process running on the host computer to identify a plurality of memory locations in the host computer that should receive the network broadcast data packets; receiving, by the hardware NIC, a response from the agent process, the response comprising a plurality of memory location identifiers associated with the plurality of memory locations; as well as The network broadcast data packets are written, by the hardware NIC, to the plurality of memory locations in the host computer that are associated with the plurality of memory location identifiers, wherein the writing comprises performing a plurality of direct memory access (DMA) operations.

12. The non-transitory computer readable medium of claim 11, wherein: The response from the agent process includes a plurality of DMA descriptors including the plurality of memory location identifiers; and The instructions also include executable code that, when executed by one or more processors, causes the processor to: The proxy process identifies a plurality of service processes based on the content of the request, sending, by the proxy process, a plurality of requests for available memory buffers to a plurality of virtual NIC interfaces associated with the plurality of service processes, receiving, by the agent process, a plurality of responses from the plurality of virtual NIC interfaces, wherein the plurality of responses include the plurality of memory location identifiers, and The plurality of DMA descriptors are generated by the agent process using the plurality of memory location identifiers.

13. The non-transitory computer readable medium of claim 12, wherein: The request identifying the plurality of memory locations comprises the network broadcast packet.

14. The non-transitory computer readable medium of claim 12, wherein: The request identifying the plurality of memory locations includes metadata about the network broadcast data packet.

15. The non-transitory computer readable medium of claim 11, wherein: The instructions also include executable code that, when executed by one or more processors, causes the processors to identify, by the hardware NIC, a plurality of service processes that should receive the network broadcast data packet based on the content of the network broadcast data packet, wherein the plurality of service processes are running on the host computer; as well as The request identifying the plurality of memory locations includes a plurality of service identifiers associated with the plurality of service processes.

16. A network traffic management device comprising a memory including programming instructions stored thereon and one or more processors configured to execute the stored programming instructions to: Network broadcast packets are received by a hardware network interface controller (NIC) connected to a host computer; Sending a request by the hardware NIC to an agent process running on the host computer to identify a plurality of memory locations in the host computer that should receive the network broadcast data packets; receiving, by the hardware NIC, a response from the agent process, the response comprising a plurality of memory location identifiers associated with the plurality of memory locations; as well as The network broadcast data packets are written, by the hardware NIC, to the plurality of memory locations in the host computer that are associated with the plurality of memory location identifiers, wherein the writing comprises performing a plurality of direct memory access (DMA) operations.

17. The network traffic management device according to claim 16, wherein: The response from the agent process includes a plurality of DMA descriptors including the plurality of memory location identifiers; and The one or more processors are further configured to execute stored programming instructions to: The proxy process identifies a plurality of service processes based on the content of the request, sending, by the proxy process, a plurality of requests for available memory buffers to a plurality of virtual NIC interfaces associated with the plurality of service processes, receiving, by the agent process, a plurality of responses from the plurality of virtual NIC interfaces, wherein the plurality of responses include the plurality of memory location identifiers, and The plurality of DMA descriptors are generated by the agent process using the plurality of memory location identifiers.

18. The network traffic management device according to claim 17, wherein: The request identifying the plurality of memory locations comprises the network broadcast packet.

19. The network traffic management device according to claim 17, wherein: The request identifying the plurality of memory locations includes metadata about the network broadcast data packet.

20. The network traffic management device of claim 16, wherein: The one or more processors are further configured to execute the stored programming instructions to identify, by the hardware NIC, a plurality of service processes that should receive the network broadcast data packet based on the content of the network broadcast data packet, wherein the plurality of service processes are running on the host computer; as well as The request identifying the plurality of memory locations includes a plurality of service identifiers associated with the plurality of service processes.