Systems and methods for handling packet fragmentation

• US 7,916,632 B1
• Filed: 09/29/2009
• Issued: 03/29/2011
• Est. Priority Date: 03/22/2002
• Status: Expired due to Fees

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Lim, Raymond Marcelino Manese, Libby, Jeffrey G.
• Primary Examiner(s): Jain; Raj K
• Application Number:
  US12/568,766
• Time in Patent Office: 546 Days
• Field of Search: None
• US Class Current: 370/229
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/36 by determining packet size, e.g. maximum transfer unit [MTU]
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/3072 Packet splitting
• 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/166 IP fragmentation; TCP segmentation

Abstract

A packet header processing engine receives a header of a packet. The received header includes a size of the packet. A maximum transfer unit size of a destination interface of the packet may be determined. The packet header processing engine determines whether the size of the packet exceeds the maximum transfer unit size of the destination interface. If the size of the packet does not exceed the maximum transfer unit size of the destination interface, the packet header processing engine generates a new header from the received header. If the size of the packet exceeds the maximum transfer unit size of the destination interface, the packet header processing engine generates a fragment header from the received header. The packet header processing engine may recycle the fragment header for further processing in addition to forming a first fragment packet from the fragment header.

Claims

1. A method, comprising:

loading, by an L2/L3 engine of a network device, header data of a first packet into a packet header memory component;

receiving, at a register of the L2/L3 engine, fragmentation information for the first packet;

processing, by an execution unit of the L2/L3 engine and based on the fragmentation information, the header data of the first packet to form a first fragment header and a second fragment header;

sending, by the execution unit, the first fragment header and the second fragment header for further processing; and

loading, by the L2/L3 engine and simultaneously with the sending, header data of a second packet into the packet header memory component.

2. The method of claim 1, where the first fragment header includes information from which a size of a remaining portion of the first packet may be determined.

3. The method of claim 2, where the first fragment header includes the size of a remaining portion of the first packet.

4. The method of claim 1, where the first fragment header includes information indicating that the first packet has been fragmented.

5. The method of claim 1, where the header data of the fragmentation information includes a maximum transfer unit size of a destination interface of the first packet.

6. The method of claim 1, where the processing further comprises:

determining whether the size of the first packet exceeds a maximum transfer unit size of the destination interface.

7. The method of claim 1, where the second fragment header is generated from the first fragment header.

8. A network device, comprising:

an input component configured to receive a packet;

a buffer connected to the input component, the buffer to store the packet, including header data and payload data for the packet, where the header data includes a size of the packet and a maximum transfer unit size of a destination interface of the packet;

a descriptor reader component connected to the input component, the descriptor reader component to receive the header data for the packet stored in the buffer and to look up descriptor information relating to the received packet header data from the input component; and

a packet header processing component coupled to the descriptor reader component, the packet header processing component to construct a packet header from the packet header data and the descriptor information from the descriptor reader component.

9. The network device of claim 8, where the packet header processing component is to send the packet header to the input component if a size of the packet exceeds the maximum transfer unit size of a destination interface for the packet.

10. The network device of claim 8, further comprising:

an output component coupled to the buffer and the packet header processing component, the output component to construct a packet from the packet header constructed by the packet header processing component and from the payload data stored in the buffer.

11. A method, comprising:

receiving, by a network device, a header of a packet, the received header including a size of the packet and a destination interface for the packet;

determining, by the network device, whether the size of the packet exceeds a maximum transfer unit size of the destination interface for the packet;

generating, by the network device, a first fragment header from the received header when the size of the packet exceeds the maximum transfer unit size of the destination interface;

sending, by the network device, the first fragment header of the packet for further processing within the network device;

receiving, by the network device from within the network device, the first fragment header, the first fragment header including information associated with a size of a remaining portion of the packet and the maximum transfer unit size of the destination interface; and

generating, by the network device, a second fragment header from the first fragment header when the size of the remaining portion of the packet exceeds the maximum transfer unit size of the destination interface.

12. The method of claim 11, further comprising:

generating, by the network device, a new header from the received header when the size of the packet does not exceed the maximum transfer unit size of the destination interface.

13. The method of claim 12, further comprising:

forming a packet including the new header.

14. The method of claim 11, further comprising:

determining, by the network device, a maximum transfer unit size of the destination interface of the packet.

15. The method of claim 11, where the first fragment header includes a size of a remaining portion of the packet.

16. The method of claim 11, where the first fragment header includes information from which a size of a remaining portion of the packet may be determined.

17. The method of claim 11, where the first fragment header includes information indicating that the packet has been fragmented.

18. The method of claim 11, further comprising:

forming a first fragment packet including the first fragment header.

19. The method of claim 11, further comprising:

determining whether the size of the remaining portion of the packet exceeds the maximum transfer unit size of the destination interface.

20. The method of claim 11, where generating the second fragment header further comprises:

simultaneously computing a checksum and computing a packet length of a second fragment associated with the second fragment header.