Abstract:
A network device receives a packet that includes a plurality of sets of fields. Sets of fields of the packet are parsed and the field sets are evaluated as soon as they are available to determine whether a processing decision can be made on the packet. Additional field sets may be parsed from the packet and obtained in parallel with determining whether a processing decision can be made, but once it is determined that a processing decision can be made, the evaluating of field sets is terminated such that any further field sets of the packet are ignored for purposes of making a processing decision for the packet.
Abstract:
Presented herein are techniques to achieve ultra low latency determination of processing decisions for packets in a network device. A packet is received at a port of a network device. A processing decision is determined in a first processing decision path based on content of the packet and one or more network policies. A processing decision is determined in a second processing decision path, in parallel with the first processing path, by accessing a table storing processing decisions. The second processing decision path can output a processing decision faster than the first processing decision path for packets that match one or more particular packet flow parameters contained in the table. A processing decision determined by the second processing decision path, if one can be made, is used, and otherwise a processing decision determined by the first processing decision path is used.
Abstract:
A packet is received at an ingress port of a network device. Based on forwarding information in the packet, an adjacency point is generated using a forwarding information database. If the packet is a routed packet, the adjacency pointer is used as an index to an entry in a media access control (MAC) table that identifies an egress port for the packet. If the packet is not a routed packet, a search is performed in the MAC table to locate an entry in the MAC table that identifies an egress port for the packet.
Abstract:
Presented herein are techniques to achieve ultra low latency determination of processing decisions for packets in a network device. A packet is received at a port of a network device. A processing decision is determined in a first processing decision path based on content of the packet and one or more network policies. A processing decision is determined in a second processing decision path, in parallel with the first processing path, by accessing a table storing processing decisions. The second processing decision path can output a processing decision faster than the first processing decision path for packets that match one or more particular packet flow parameters contained in the table. A processing decision determined by the second processing decision path, if one can be made, is used, and otherwise a processing decision determined by the first processing decision path is used.
Abstract:
A packet is received at an ingress port of a network device. Based on forwarding information in the packet, an adjacency point is generated using a forwarding information database. If the packet is a routed packet, the adjacency pointer is used as an index to an entry in a media access control (MAC) table that identifies an egress port for the packet. If the packet is not a routed packet, a search is performed in the MAC table to locate an entry in the MAC table that identifies an egress port for the packet.
Abstract:
Techniques are provided for optimizing storage of address information in switch device databases. A control packet is received from a source host. An address associated with a host is determined. The address comprises a first and second address component. The first address component is stored in a first database and is mapped to an index value that is stored in the first database. The index value is also stored in a second database along with the second address component. The first database may also be examined to determine whether the first address component is stored in the first database. If the first address component is stored in the first database, the index value mapped to the first address component is retrieved. The second database is examined to determine whether the index value and the second address component are stored in the second database.
Abstract:
Techniques are provided for optimizing storage of address information in switch device databases. A control packet is received from a source host. An address associated with a host is determined. The address comprises a first and second address component. The first address component is stored in a first database and is mapped to an index value that is stored in the first database. The index value is also stored in a second database along with the second address component. The first database may also be examined to determine whether the first address component is stored in the first database. If the first address component is stored in the first database, the index value mapped to the first address component is retrieved. The second database is examined to determine whether the index value and the second address component are stored in the second database.
Abstract:
A network device receives a packet that includes a plurality of header fields. The packet is parsed to sequentially obtain the plurality of header fields. One or more header fields not yet available at the network device are predicted based on one or more header fields that are available at the network device. A network processing decision is generated for the packet based on the predicted one or more header fields and the one or more header fields that are available at the network device.
Abstract:
Presented herein are techniques to achieve ultra low latency determination of processing decisions for packets in a network device. A packet is received at a port of a network device. A processing decision is determined in a first processing decision path based on content of the packet and one or more network policies. A processing decision is determined in a second processing decision path, in parallel with the first processing path, by accessing a table storing processing decisions. The second processing decision path can output a processing decision faster than the first processing decision path for packets that match one or more particular packet flow parameters contained in the table. A processing decision determined by the second processing decision path, if one can be made, is used, and otherwise a processing decision determined by the first processing decision path is used.