Packet coalescing

• US 8,718,096 B2
• Filed: 12/29/2010
• Issued: 05/06/2014
• Est. Priority Date: 11/16/2004
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Makineni, Srihari, Iyer, Ravishankar, Sen, Sujoy, Newell, Donald, Zhao, Li, Minturn, David
• Primary Examiner(s): Nguyen, Brian D
• Assistant Examiner(s): NGUYEN, TOAN D
• Application Number:
  US12/980,682
• Publication Number:
  US 20110090920A1
• Time in Patent Office: 1,224 Days
• Field of Search: 370/392, 370/393, 370/394, 370/463, 709/250
• US Class Current: 370/474
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 49/20 Support for services
• 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/166 IP fragmentation; TCP segmentation

Abstract

In general, in one aspect, the disclosures describes a method that includes receiving multiple ingress Internet Protocol packets, each of the multiple ingress Internet Protocol packets having an Internet Protocol header and a Transmission Control Protocol segment having a Transmission Control Protocol header and a Transmission Control Protocol payload, where the multiple packets belonging to a same Transmission Control Protocol/Internet Protocol flow. The method also includes preparing an Internet Protocol packet having a single Internet Protocol header and a single Transmission Control Protocol segment having a single Transmission Control Protocol header and a single payload formed by a combination of the Transmission Control Protocol segment payloads of the multiple Internet Protocol packets. The method further includes generating a signal that causes receive processing of the Internet Protocol packet.

Claims

1. A method, comprising:

receiving network packets transmitted over a network, multiple ones of the network packets having the same set of multiple header structures within, each of the multiple ones of the network packets belonging to a respective flow of network packets;

for multiple respective flows of network packets, maintaining, at least;

(1) data of payloads of network packets being coalesced for the multiple respective flows; and

(2) a respective number of packets being coalesced for the multiple respective flows;

determining a first of the received network packets is of a flow matching a one of the multiple respective flows;

adding the data of the payload of the first of the received network packets to the data of payloads of network packets being coalesced for the one of the multiple respective flows;

incrementing the respective number of packets being coalesced for the one of the multiple respective flows;

determining a second of the received network packets is of a flow matching the one of the multiple respective flows;

determining that a protocol stack should process data of the network packets corresponding to at least one of the respective flows;

based on the determining that the protocol stack should process data of the network packets corresponding to the at least one of the respective flows, generating data corresponding to a network packet having;

(1) the same set of multiple header structures found within each of the multiple network packets; and

(2) a payload corresponding to a combination of the data of the payloads of the network packets being coalesced for the respective flow; and

causing protocol stack processing of the generated data corresponding to a network packet instead of the multiple received network packets associated with the flow; and

not adding data of the payload of the second of the received network packets to the payloads of network packets being coalesced for the one of the multiple respective flows.

2. The method of claim 1,

wherein the multiple header structures comprise an Internet Protocol (IP) header and a Transmission Control Protocol (TCP) header;

and

wherein the flows comprise flows determined by data within the header structures.

3. The method of claim 1,

wherein the multiple header structures comprise at least two header structures.

4. The method of claim 1,

wherein the generating the network packet comprises determining new values for fields within the header structures.

5. A computer program, disposed on a non-transitory computer readable storage medium, comprising instructions for causing a device to:

receive network packets transmitted over a network, multiple ones of the network packets having the same set of multiple header structures within, each of the multiple ones of the network packets belonging to a respective flow of network packets;

for multiple respective flows of network packets, maintain, at least;

(1) data of payloads of network packets being coalesced for the multiple respective flows; and

(2) a respective number of packets being coalesced for each of multiple respective flows;

determine a first of the received network packets is of a flow matching a one of the multiple respective flows;

add the data of the payload of the first of the received network packets to data of payloads of network packets being coalesced for the one of the multiple respective flows;

increment the respective number of packets being coalesced for the one of the multiple respective flows;

determine a second of the received network packets is of a flow matching the one of the multiple respective flows;

determine that a protocol stack should process data of the network packets corresponding to at least one of the respective flows;

based on a determination that the protocol stack should process data of the network packets corresponding to the at least one of the respective flows, generate data corresponding to a network packet having;

(1) the same set of multiple header structures found within each of the multiple network packets; and

(2) a payload corresponding to a combination of the data of the payloads of the network packets being coalesced for the respective flow; and

cause protocol stack processing of the generated data corresponding to a network packet instead of the multiple received network packets associated with the flow; and

not add data of the payload of the second of the received network packets to the payloads of network packets being coalesced for the one of the multiple respective flows.

6. The computer program of claim 5,

wherein the multiple header structures comprise an Internet Protocol (IP) header and a Transmission Control Protocol (TCP) header;

and

wherein the flows comprise flows determined by data within the header structures.

7. The computer program of claim 5,

wherein the multiple header structures comprise at least two header structures.

8. The computer program of claim 5,

wherein the instructions to cause the device to generate the network packet comprise instructions to determine new values for fields within the header structures.

9. A network device, comprising circuitry configured to, when in operation:

receive network packets transmitted over a network, multiple ones of the network packets having the same set of multiple header structures within, each of the multiple ones of the network packets belonging to a respective flow of network packets;

for multiple respective flows of network packets, maintain, at least;

(1) data of payloads of network packets being coalesced for each of the multiple respective flows; and

(2) a respective number of packets being coalesced for each of multiple respective flows;

determine a first of the received network packets is of a flow matching a one of the multiple respective flows;

add data of the payload of the first of the received network packets to the data of payloads of network packets being coalesced for the one of the multiple respective flows;

increment the respective number of packets being coalesced for the one of the multiple respective flows;

determine a second of the received network packets is of a flow matching the one of the multiple respective flows; and

determine that a protocol stack should process data of the network packets corresponding to at least one of the respective flows;

based on a determination that the protocol stack should process data of the network packets corresponding to the at least one of the respective flows, generate data corresponding to a network packet having;

(1) the same set of multiple header structures found within each of the multiple network packets; and

(2) a payload corresponding to a combination of the data of the payloads of the network packets being coalesced for the respective flow; and

cause the protocol stack processing of the generated data corresponding to the network packet instead of the multiple received network packets associated with the flow; and

not add data of the payload of the second of the received network packets to the payloads of network packets being coalesced for the one of the multiple respective flows.

10. The network device of claim 9,

wherein the multiple header structures comprise an Internet Protocol (IP) header and a Transmission Control Protocol (TCP) header;

and

wherein the flows comprise flows determined by data within the header structures.

11. The network device of claim 9,

wherein the multiple header structures comprise at least two header structures.

12. The network device of claim 9,

wherein the circuitry configured to generate the network packet comprises circuitry configured to determine new values for fields within the header structures.