Multiple parallel packet routing lookup

• US 6,212,183 B1
• Filed: 08/22/1997
• Issued: 04/03/2001
• Est. Priority Date: 08/22/1997
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Wilford, Bruce A.
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): Pizarro, Ricardo M.
• Application Number:
  US08/917,654
• Time in Patent Office: 1,320 Days
• Field of Search: 370/392, 370/393, 370/394, 370/396, 370/397, 370/398, 370/399, 370/400
• US Class Current: 370/392
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/54 Organization of routing tables

Abstract

The invention provides a method and system for routing information lookup for packets using a routing protocol such as IP. Routing information which has been determined responsive to the packet header, which includes a destination address, a source address, and an input interface for the packet. Routing lookup is performed in response to at least one set of selected routing information, using a lookup table which includes tags both for the routing information and for a bitmask length (thus indicating the generality or scope of the routing information for the routing lookup). The lookup table is structured so that addresses having the most common bitmask length are addressed first, but that more specific addresses are still considered when they are present. It has been discovered that most internet addresses can be found by reference to 24-bit or 21-bit IP addresses, after which 16-bit, 12-bit, and finally 32-bit IP addresses are considered. Lookup flags indicate when a relatively uncommon but more specific 32-bit IP address match is available. A memory controller pipelines the lookup requests to a hash table memory, flushes superfluous requests when a lookup result is found, and handles cases relating to 32-bit IP address matches.

Claims

1. A method, including the steps of

receiving a packet header, said packet header including header information;

determining a packet treatment identifier responsive to said header information, said packet treatment identifier including a destination address; and

using said packet treatment identifier to access a memory having information regarding treatment of packets, said information being responsive to a length field for said header information, said memory including a plurality of entries matching said header information and differing with regard to said length field, said entries associated with packet routing information, and

wherein said length field indicates a longest match for said destination address included in said header information.

2. A method as in claim 1, wherein said destination address is a destination IP address.

3. A method as in claim 1, wherein said packet treatment identifier includes a source IP address.

4. A method as in claim 1, wherein said memory includes a plurality of entries matching said destination address and responsive to a multicast packet.