Zero copy method for receiving data by a network interface

• US 7,620,726 B2
• Filed: 01/28/2005
• Issued: 11/17/2009
• Est. Priority Date: 10/14/1997
• Status: Expired due to Fees

• Current Assignee: Alacritech, Inc.
• Original Assignee: Alacritech, Inc.
• Inventors: Higgen, David A., Philbrick, Clive M., Boucher, Laurence B., Craft, Peter K.
• Primary Examiner(s): Maung; Zarni
• Application Number:
  US11/046,337
• Publication Number:
  US 20050198198A1
• Time in Patent Office: 1,754 Days
• Field of Search: 709/203, 709223-229, 709/230, 709/245, 709/250
• US Class Current: 709/230
• CPC Class Codes: G02B 7/36 using image sharpness techniques , e.g. image processing techniques for generating autofocus signals image data processing per se G06T; in cameras having a solid state image sensor H04N23/67
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/9042 Separate storage for different parts of the packet, e.g. header and payload
• CPC Class Codes: H04L 49/9063 Intermediate storage in different physical parts of a node or terminal
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/12 Protocol engines
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/166 IP fragmentation; TCP segmentation
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A host CPU runs a network protocol processing stack that provides instructions not only to process network messages but also to allocate processing of certain network messages to a specialized network communication device, offloading some of the most time consuming protocol processing from the host CPU to the network communication device. By allocating common and time consuming network processes to the device, while retaining the ability to handle less time intensive and more varied processing on the host stack, the network communication device can be relatively simple and cost effective. The host CPU, operating according to instructions from the stack, and the network communication device together determine whether and to what extent a given message is processed by the host CPU or by the network communication device.

Claims

1. A method for receiving data from a network by a local host having a processor running an application and a memory that is accessible by the processor, the local host being connected to the network by a network interface, the data prepended with a TCP header, the method comprising:

identifying, by the application, a location in the memory to place the data;

providing a description of the location to the network interface; and

placing, by the network interface, the data free of the TCP header into the memory at the location.

2. The method of claim 1, wherein the application includes a file server protocol.

3. The method of claim 1, wherein providing a description of the location to the network interface includes providing a buffer to the network interface.

4. The method of claim 1, wherein providing a description of the location to the network interface includes providing a list of host buffer address and length pairs to the network interface.

5. The method of claim 1, wherein providing a description of the location to the network interface includes providing a memory descriptor list (MDL) to the network interface.

6. The method of claim 1, further comprising sending, by the network interface, an acknowledgment (ACK) to the remote host to acknowledge receipt of the data, while placing the data into the memory.

7. The method of claim 1, further comprising sending, by the network interface, a window update to the remote host to signal acceptance of the data by the application, after placing the data into the memory.

8. The method of claim 1, wherein the data is placed into the memory without the data being touched by the processor.

9. The method of claim 1, further comprising:

establishing, by the processor, a TCP connection corresponding to the TCP header; and

offloading the TCP connection to the network interface.

10. The method of claim 1, wherein the network interface includes a device driver for a network interface device, and wherein providing a description of the location to the network interface includes providing a data structure to the device driver.

11. The method of claim 1, wherein the data is part of a message received in a plurality of packets, and identifying a location in the memory to place the data includes allocating sufficient space in the memory to store the message.

12. A method for receiving a message from a network by a local host having a processor running an application and a memory that is accessible by the processor, the local host being connected to the network by a network interface, the message including a plurality of packets each having a TCP header, the method comprising:

identifying, by an application of the local host, a destination in the memory to place the data;

providing a description of the destination to the network interface; and

placing, by the network interface, data from each packet free of any TCP header into the memory at the destination.

13. The method of claim 12, wherein providing a description of the destination to the network interface includes providing a buffer to the network interface.

14. The method of claim 12, wherein providing a description of the destination to the network interface includes providing a list of host buffer address and length pairs to the network interface.

15. The method of claim 12, wherein providing a description of the destination to the network interface includes providing a memory descriptor list (MDL) to the network interface.

16. The method of claim 12, further comprising sending, by the network interface, ACKs back to the remote host to acknowledge receipt of the data, while placing the data into the memory.

17. The method of claim 12, further comprising sending, by the network interface, a window update to the remote host to acknowledge acceptance of the data by the application, after placing the data into the memory.

18. The method of claim 12, wherein the data is placed into the destination without the data being touched by the processor.

19. A system for receiving data from a network by a local host having a processor running an application and a memory that is accessible by the processor, the local host connected to the network by a network interface, the data prepended with a TCP header, the system comprising:

an application running on the processor to identify a location in the memory in which to place the data, and to create a data structure that provides a description of the location; and

a mechanism of the network interface that uses the data structure to place the data free of the TCP header into the memory at the location.

20. The system of claim 19, wherein the description includes a buffer of the memory.

21. The system of claim 19, wherein the data structure includes a scatter-gather list of host buffer address and length pairs.

22. The system of claim 19, wherein the data structure includes a memory descriptor list (MDL).

23. The system of claim 19, wherein the mechanism includes a direct memory access (DMA) engine.

24. The system of claim 19, further comprising:

a protocol processing stack that is executable by the processor to establish a TCP connection corresponding to the TCP header and to offload the TCP connection to the network interface.

25. The system of claim 19, wherein the network interface includes a device driver for a network interface device, and the data structure that provides a description of the location to the network interface is passed from the device driver to the network interface device.