The present invention is related to an Internet Protocol (IP) router or a Multiprotocol Label Switching (MPLS) router and network processors for routing packets over a network. Further, the present invention is related to a method for routing packets over a network.
High quality Internet Protocol (IP) and Multiprotocol Label Switching (MPLS) routers use network processors (NP) for their packet forwarding tasks. These network processors are programmable devices optimised (optionally with dedicated hardware auxiliary circuits) to do the processing of e.g. IP and MPLS protocols. As a single processor is hardly able to process at wirespeed the 25 to 100 million packets per second of Optical Carrier interfaces, many network processors use a multiprocessor engine whereby each of the engines may run multiple threads. In such architecture, multiple packets are processed at the same time. As the processing time of an individual packet may vary, a dedicated function is required to ensure that the network processor maintains packet order.
The packet reordering function in state of the art network processors is engineered to keep packet order only between relevant packets, i.e. typically packets of the same end to end flow. As the reordering between end to end flows is not scalable, means are introduced, such as a hashing function based on packet parameters, in order to classify packets in “classes”. This is performed before the packet processing is started. Within such a class, the packet order is maintained.
The above solution does not classify packets based on their processing time. It is even not possible to do so, as the processing time is only known when packet processing is ongoing or finished. Hence the prior art solution, i.e. classification based on a hashing function, results in a classification of packets with a large variety in processing time within each of the classes. The reordering of the packets within such a class may not be very efficient because the reordering element of the network processor has to wait for the packet with the largest processing time before all packets can be reordered and sent out subsequently. The network processor is not utilised efficiently during this waiting time.
The present invention aims to provide a novel method and apparatus for forwarding packets efficiently in a network processor.
The present invention concerns a method for packet reordering in a network processor, comprising the steps of:
Preferably, the step of determining the nominal packet processing time comprises the steps of:
Further, the processing time is advantageously expressed in time units, such as real time but more preferably time tokens, indicating a relative time within the network processor. Such tokens can provide quicker processing of time data.
The method for packet reordering of the present invention can further be characterised in that the plurality of tiers comprises one first tier and at least one subsequent tier, said first tier being used for transfer of short processing time packets.
A suitable sorting algorithm for the first tier can e.g. be based on the sequence number of the packet. The suitable sorting algorithm for the subsequent tiers can e.g. be based on the timestamp of the packet.
The step of collecting eligible packets from the groups in a collector for forwarding can comprise a selection of a tier according to a weighed round robin algorithm.
In a preferred embodiment of the present invention, a packet from a tier is eligible for collecting if the actual time is later than the timestamp of said packet+the maximum processing time of a packet associated to said tier.
Another embodiment of the present invention concerns a reordering unit implementing the method of the present invention.
A further embodiment of the present invention is a network processor comprising the reordering unit of the present invention.
The present invention, which provides a solution to the problems of the state of the art concerns packet classification by the network processor during packet processing. This classification is based on the processing method and corresponding time. Each class of this new reordering principle corresponds to a packet processing time interval, a result of the applied processing method(s). The processing time intervals of two classes may be (partly) overlapping. The reordering of packets in a particular class only has to cope with a well known processing time interval defined for that class, which is much smaller than the global delta processing time of all packets processed by the Network processor (NP).
The solution can be applied to reorder traffic in one packet processing component or between multiple packet processing components.
The network processor code is able to make a classification of the packets based on processing time and method at packet processing time. The code overhead is very small. This classification allows one to organise the reordering per class, whereby the delta processing time of packets in one class is much smaller than the overall delta processing time. The present invention will now be illustrated by an example of an embodiment.
Packets are foreseen of parameters such as a packet reference number, a timestamp, and a sequence number. Typically, all or some of the parameters need to be read and/or passed onto the next level to allow proper treatment in the reordering unit. E.g. between the dispatch unit 5 and the processing units 6, packet reference numbers are passed (9), while the dispatch unit 5 passes packet reference numbers, timestamps and sequence numbers to the reordering unit 7 (8).
Processing of a packet by a processing unit consists of a sequence of actions. A different type of packet will require a different type of processing, which is reflected in a different combination (a different sequence) of actions. Every possible action also has its nominal processing time.
For example:
And the nominal processing times for the possible actions:
It is also possible to replace the nominal processing time by a number of processing time tokens, for ease of implementation. Each token represents e.g. a processing time unit.
During the processing of a packet, each action is logged. A packet is thus associated to a specific processing time which can be calculated by addition of all the nominal processing times for all the actions required to process the packet. For type 3, the total processing time will thus be equal to time 1+time 2+time 3. Further, all packets are associated to an array logging the processing actions, so for a processed packet of type 3, the array looks like
The total nominal processing time is used to assign it to a tier (10), as can be seen on
The ranges are non-overlapping, so that every packet is associated with only one nominal processing time, which is only associated with one tier. Every processed packet can thus be assigned to only one processing tier.
Packets arriving at their assigned tier, have to be reordered before they are passed on to a collector 13 which is at the end of the network processor. Since all packets that are present in a tier have about the same processing time (the difference between processing times of different packets is small since the tier assignment was done on the basis of processing time), the tier reordering can be optimised to suit the needs. E.g., tier 1 (11) can be used for fast processed packets, while tier 2 (12) and up can be used for packets with medium or long processing time.
If different tiers have a reordered packet waiting for collection, the collector 13 can collect the packets in a weighted round robin mode (the lower tiers may have e.g. higher weights).
A filled bucket lookup engine 16 is used. Processed packets are directly inserted in the corresponding sequence number bucket (15). A packet is eligible to be passed (14) to the collector 13 if the actual time is later than the timestamp+the maximum processing time of a packet associated to tier 1 or if the packet has the sequence number following the sequence number of the previously collected packet of tier 1. This reorder engine can work at wirespeed and treats typically the fastest processed packets.
An overview of the packet flow in a network processor according to the present invention is given in
Number | Date | Country | Kind |
---|---|---|---|
02290817 | Apr 2002 | EP | regional |
Number | Name | Date | Kind |
---|---|---|---|
4581734 | Olson et al. | Apr 1986 | A |
5150358 | Punj et al. | Sep 1992 | A |
5278830 | Kudo | Jan 1994 | A |
5666161 | Kohiyama et al. | Sep 1997 | A |
5894586 | Marks et al. | Apr 1999 | A |
5926459 | Lyles et al. | Jul 1999 | A |
6000053 | Levine et al. | Dec 1999 | A |
6058114 | Sethuram et al. | May 2000 | A |
6075791 | Chiussi et al. | Jun 2000 | A |
6091709 | Harrison et al. | Jul 2000 | A |
6104700 | Haddock et al. | Aug 2000 | A |
6134217 | Stiliadis et al. | Oct 2000 | A |
6148324 | Ransom et al. | Nov 2000 | A |
6262983 | Yoshizawa et al. | Jul 2001 | B1 |
6272109 | Pei et al. | Aug 2001 | B1 |
6292489 | Fukushima et al. | Sep 2001 | B1 |
6636481 | Yamaguchi et al. | Oct 2003 | B1 |
6704346 | Mansfield | Mar 2004 | B1 |
6714517 | Fawaz et al. | Mar 2004 | B1 |
6714546 | Watanabe et al. | Mar 2004 | B1 |
6751194 | Ueno | Jun 2004 | B1 |
6801530 | Brandt et al. | Oct 2004 | B1 |
6826147 | Nandy et al. | Nov 2004 | B1 |
6985441 | Acharya | Jan 2006 | B1 |
6990120 | Lindgren et al. | Jan 2006 | B1 |
7050403 | Mononen | May 2006 | B2 |
7095715 | Buckman et al. | Aug 2006 | B2 |
7130277 | Fujii et al. | Oct 2006 | B2 |
7130307 | Nakamura et al. | Oct 2006 | B2 |
7149184 | Takada et al. | Dec 2006 | B2 |
7158519 | Kanakubo | Jan 2007 | B2 |
7215637 | Ferguson et al. | May 2007 | B1 |
7366165 | Kawarai et al. | Apr 2008 | B2 |
20010048690 | Magill et al. | Dec 2001 | A1 |
20020044563 | Magill et al. | Apr 2002 | A1 |
20020091852 | Frazier et al. | Jul 2002 | A1 |
20020122387 | Ni | Sep 2002 | A1 |
20020122424 | Kawarai et al. | Sep 2002 | A1 |
20030053485 | Chuah et al. | Mar 2003 | A1 |
20030076848 | Bremler-Barr et al. | Apr 2003 | A1 |
20030081600 | Blaker et al. | May 2003 | A1 |
20030126272 | Corl et al. | Jul 2003 | A1 |
Number | Date | Country |
---|---|---|
2 349 296 | Oct 2000 | GB |
Number | Date | Country | |
---|---|---|---|
20030189931 A1 | Oct 2003 | US |