Obtaining a destination address so that a network interface device can write network data without headers directly into host memory

• US 7,461,160 B2
• Filed: 06/29/2004
• Issued: 12/02/2008
• 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., Blightman, Stephen E. J., Starr, Daryl D.
• Primary Examiner(s): Maung; Zarni
• Application Number:
  US10/881,271
• Publication Number:
  US 20040240435A1
• Time in Patent Office: 1,617 Days
• Field of Search: 709/250, 709/230, 709/231, 709/228, 709/243, 709/236, 709/225, 709/245
• US Class Current: 709/230
• CPC Class Codes: G06F 5/10 having a sequence of storage locations each being individually accessible for both enqueue and dequeue operations, e.g. using random access memory G06F5/065 takes precedence
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/901 using storage descriptor, e.g. read or write pointers
• 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/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• 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 69/321 : Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04Q 2213/13093 : Personal computer, PC
• CPC Class Codes: H04Q 2213/13103 : Memory
• CPC Class Codes: H04Q 2213/13204 : Protocols
• CPC Class Codes: H04Q 2213/13299 : Bus
• CPC Class Codes: H04Q 2213/1332 : Logic circuits
• CPC Class Codes: H04Q 2213/13345 : Intelligent networks, SCP
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking

Abstract

A Network Interface device (NI device) coupled to a host computer receives a multi-packet message from a network (for example, the Internet) and DMAs the data portions of the various packets directly into a destination in application memory on the host computer. The address of the destination is determined by supplying a first part of the first packet to an application program such that the application program returns the address of the destination. The address is supplied by the host computer to the NI device so that the NI device can DMA the data portions of the various packets directly into the destination. In some embodiments the NI device is an expansion card added to the host computer, whereas in other embodiments the NI device is a part of the host computer.

Claims

1. A method for use by a network interface for a host computer running an application, the method comprising:

running, on the network interface, a TCP connection for the application;

receiving, by the network interface, multi-packet message including a first packet and a plurality of subsequent packets, each of the plurality of subsequent packets containing a TCP header portion, an IP header portion and a data portion;

passing, by the network interface, at least a portion of the first packet of the multi-packet message to the host computer;

receiving, by the network interface, an indication of a destination in memory on the host computer, the destination controlled by the application; and

writing, by the network interface, the data portions of the subsequent packets into the destination without writing any TCP header portion into the destination and without writing any IP header portion into the destination.

2. The method of claim 1, wherein the multi-packet message has a data payload, and writing the data portions of the subsequent packets into the destination includes writing the entire data payload by the network interface into the destination.

3. The method of claim 1, wherein the network interface is an intelligent network interface card (INIC) that includes a DMA engine, and writing the data portions of the subsequent packets into the destination includes writing the data portions by DMA.

4. The method of claim 1, further comprising storing the address of the destination with the TCP connection on the network interface.

5. A method comprising:

receiving, by a network interface device for a host computer, a message containing a plurality of packets having a TCP header and a data portion;

passing at least a portion of a first of the packets from the network interface device to the host computer, wherein said at least a portion includes a session layer header;

receiving, by the network interface device, an indication of a destination in host memory, in response to the passing at least a portion of the first packet to the host computer; and

transferring, by the network interface device, the data portions of any of the plurality of packets subsequent to the first packet into the destination without writing any TCP header portion of any of the subsequent packets into the destination.

6. The method of claim 5, wherein the network interface device comprises an expansion card and an application specific integrated circuit (ASIC).

7. The method of claim 5, wherein only a portion of the first packet is passed to the host computer when passing at least a portion of the first packet to the host computer, such that the host computer generates the indication of the destination without receiving the entire first packet.

8. The method of claim 5, wherein the host computer includes a motherboard, and wherein the network interface device is disposed on the motherboard.

9. A method comprising:

receiving, by a network interface device for a host computer, a message containing a first packet and a plurality of subsequent packets having a TCP header portion and a data portion, the TCP header portion indicating an application in the host computer;

passing a first part of the first packet, but not a second part of the first packet, from the network interface device to the host computer, the first part of the first packet including a session layer header portion;

receiving, by the network interface device from the host computer, an indication of a destination in host memory provided by the application; and

transferring, by the network interface device, the data portions of the subsequent packets into the destination without writing any TCP header portion of any of the subsequent packets into the destination.

10. The method of claim 9, further comprising:

transferring, by the network interface device, the second part of the first packet from the network interface device and into the destination.

11. The method of claim 9, wherein the indication of the destination in host memory comprises a plurality of addresses and a plurality of lengths.

12. The method of claim 9, wherein the message is communicated over a TCP/IP connection, and wherein the TCP/IP connection is setup before passing the first part of the first packet from the network interface device to the host computer.

13. The method of claim 9, wherein the application determines from the session layer header how much session layer data is contained in the message, and wherein the application determines how big the destination should be in order to contain all the session layer data of the message, and wherein all the session layer data is written into the destination such that no TCP headers are present in the destination and such that no IP headers are present in the destination.

14. The method of claim 13, wherein all the session layer data is written into the destination and such that no session layer headers are present in the destination.