Parsing a packet header

• US 8,782,199 B2
• Filed: 10/18/2002
• Issued: 07/15/2014
• Est. Priority Date: 10/14/1997
• Status: Expired due to Fees

• Current Assignee: Alacritech, Inc.
• Original Assignee: A Tech LLC
• Inventors: Boucher, Laurence B., Blightman, Stephen E. J., Craft, Peter K., Higgen, David A., Philbrick, Clive M., Starr, Daryl D.
• Primary Examiner(s): BURGESS, BARBARA N
• Application Number:
  US10/277,604
• Publication Number:
  US 20040078480A1
• Time in Patent Office: 4,288 Days
• Field of Search: 709/224, 709/203, 709/223
• US Class Current: 709/224
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/193 at the transport layer, e.g. TCP related
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 47/43 Assembling or disassembling of packets, e.g. segmentation and reassembly [SAR]
• 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/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

An intelligent network interface card (INIC) or communication processing device (CPD) works with a host computer for data communication. The device provides a fast-path that avoids protocol processing for most messages, greatly accelerating data transfer and offloading time-intensive processing tasks from the host CPU. The host retains a fallback processing capability for messages that do not fit fast-path criteria, with the device providing assistance such as validation even for slow-path messages, and messages being selected for either fast-path or slow-path processing. A context for a connection is defined that allows the device to move data, free of headers, directly to or from a destination or source in the host. The context can be passed back to the host for message processing by the host. The device contains specialized hardware circuits that are much faster at their specific tasks than a general purpose CPU. A preferred embodiment includes a trio of pipelined processors devoted to transmit, receive and utility processing, providing full duplex communication for four Fast Ethernet nodes.

Claims

1. A method for use with a computer system, comprising:

receiving, with a network controller for a host computer, a packet that includes a header, the header indicating a first characteristic that is associated with a transport layer of a multiple layer protocol stack and a second characteristic that is associated with an application layer of the stack;

parsing the packet with the network controller to extract said first and second characteristics, wherein said first characteristic includes an identification of a Transmission Control Protocol (TCP) connection, and said second characteristic includes a length of application data being received; and

passing a handle from the network controller to the host computer to indicate said first and second characteristics, wherein the handle associates the packet with a flow that corresponds to the TCP connection, and indicates an amount of said application data to be stored in the host computer.

2. The method of claim 1, wherein the act of passing comprises:

passing the handle to another layer of the protocol stack.

3. The method of claim 1, wherein said first characteristic comprises:

a port number associated with the application.

4. The method of claim 1, wherein the TCP connection is stored as a CCB in the network controller, and the CCB includes information regarding a data link layer.

5. The method of claim 1, wherein said first characteristic comprises:

a type of the packet.

6. The method of claim 1, further comprising:

selectively transmitting acknowledgement packets based on said first characteristic.

7. The method of claim 1, further comprising:

storing data associated with the packet in a region of memory that is used by execution of an application based on said first and second characteristics.

8. The method of claim 7, wherein the network controller comprises means for parsing the packet, and wherein said identification is a combination of a TCP source port, a TCP destination port, an IP source address, and an IP destination address, and wherein the handle associates the packet with a flow.

9. The method of claim 7, wherein the computer system comprises:

means for determining a memory address at which to store the application data.

10. The method of claim 7, wherein the network controller is a TCP offload device.

11. The method of claim 7, further comprising:

passing an indication of said first characteristic to the network controller, and wherein the network controller matches said first characteristic extracted from the packet with said first characteristic passed to the network interface device.

12. The method of claim 7, further comprising:

receiving onto the network controller from the protocol stack an indication of the region of memory.

13. The method of claim 7, further comprising:

a step for receiving onto the network controller from the protocol stack an indication of the region of memory.

14. The method of claim 7, wherein the handle is a header buffer, and wherein the header buffer contains status information about the packet.

15. The method of claim 7, wherein the handle is a header buffer, and wherein the header buffer specifies a fast-path connection, the fast-path connection being identified by a TCP source port, a TCP destination port, an IP source address, and IP destination address.

16. The method of claim 1, wherein the transport layer comprises TCP.

17. The method of claim 1, wherein the act of receiving comprises:

receiving the packet from a network.

18. The method of claim 1, wherein the handle comprises an IP address and a TCP port.

19. The method of claim 1, wherein the handle comprises a number corresponding to a context.

20. The method of claim 1, wherein the handle is passed to the network controller.

21. The method of claim 1, further comprising:

using the packet to obtain memory space for another packet.

22. An apparatus for use with a computer system capable of executing software of a protocol stack to extract at least first and second characteristics of a packet, comprising:

an interface adapted to receive the packet, the packet including a header indicating said first and second characteristics, wherein said first characteristic includes an identification of a Transmission Control Protocol (TCP) connection, and said second characteristic includes a length of application data being received;

a circuit adapted to parse the header to extract said first and second characteristics of the packet without causing the computer system to execute the software; and

a direct memory access (DMA) engine to copy the application data to a memory of the computer system controlled by the application.

23. The apparatus of claim 22, wherein said first characteristic comprises:

a port number being associated with the application.

24. The apparatus of claim 22, wherein the circuit comprises means for parsing the header.

25. The apparatus of claim 22, wherein said first characteristic comprises:

a type of the packet.

26. The apparatus of claim 22, wherein the circuit is further adapted to:

use said first characteristic to associate the packet with a flow.

27. The apparatus of claim 22, wherein the apparatus comprises a network controller.

28. A computer system comprising:

a processor adapted to execute software of a network stack to process a packet; and

a peripheral device adapted to;

receive the packet, the packet including a header indicating an identification of a Transmission Control Protocol (TCP) connection and a length of application data being received, the packet further including a portion of the application data,

parse the header to extract said identification and length,

provide the identification and length to the processor to obtain a final destination for the application data, and

send the application data to the final destination.

29. The computer system of claim 28, wherein the software comprises a network layer.

30. The computer system of claim 28, wherein said identification comprises:

a port number associated with the application.

31. The computer of claim 28, further comprising:

means for determining a memory address at which to store the application data.

32. The computer system of claim 28, wherein said identification comprises:

a type of the packet.

33. The computer system of claim 28, wherein the peripheral device is further adapted to:

use said identification to associate the packet with a flow.

34. The computer system of claim 28, wherein the peripheral device is further adapted to:

provide zero-copy support for an upper layer protocol layer, wherein the upper layer protocol layer is a layer that is higher than a transport layer.

35. The computer system of claim 34, wherein said identification is a combination of a TCP source port, a TCP destination port, an IP source address, and an IP destination address.

36. The computer system of claim 35, wherein the peripheral device receives an indication of the final destination from the processor, and wherein the peripheral device provides said zero-copy support by transferring a data payload of the packet from the peripheral device directly into the final destination.

37. The computer system of claim 36, wherein the stack includes a transport processing layer, and wherein the stack performs substantially no TCP processing on the packet, and wherein the peripheral device performs substantially all TCP processing on the packet.

38. The computer system of claim 28, wherein the peripheral device comprises a network controller.

39. The computer system of claim 28, wherein the characteristic is that the packet is a fast-path packet.

40. The computer system of claim 28, wherein the peripheral device is further adapted to:

choose between slow-path processing the packet and fast-path processing the packet.

41. The computer system of claim 28, wherein the peripheral device is further adapted to:

receive an indication of said identification onto said peripheral device from said processor, the peripheral device matching said identification extracted from the header with said identification received onto the peripheral device from said processor.

42. A method for use with a computer system, comprising:

receiving, by a network controller for the computer system, a packet that includes a header, the header including a TCP source port, a TCP destination port, an IP source address, and an IP destination address, and wherein a TCP connection is identified by the TCP source port, the TCP destination port, the IP source address, and the IP destination address;

parsing the packet with the network controller to extract said TCP source port, said TCP destination port, said IP source address and said IP destination address, including creating an indication of the TCP connection, and determining a length of application data to be stored in the computer system, wherein the packet includes part but not all of the application data;

sending an identification of the TCP connection and said length from the network controller to the computer system to obtain a destination for storing said application data; and

storing said application data in said destination by said network controller.