Abstract: Technologies for flexible tree-based lookups include an network device that receives a network packet. The network device classifies the network packet to determine a packet type and extracts multiple fields from the network packet to generate a field vector. The fields are selected based on the packet type. The field vector includes words that are associated with the fields. The network device builds a tree representation of the field vector. The tree representation includes a leaf node corresponding to each word of the field vector and one or more root nodes. The network device executes an iterative lookup over the tree representation and, if matching, may perform an action associated with the iterative lookup. To execute the lookup, the network device may determine whether a search key for each node exactly matches a search rule, up to a root node. Other embodiments are described and claimed.

Abstract: Disclosed is a mechanism for maintaining a single lookup table entry for symmetric/bidirectional flows. Multiple recipes are stored for each flow. A recipe is employed to select address information from an incoming packet header based on the packet's direction. The address information and an index are employed to generate a lookup key to find the single lookup table entry with the pertinent switching information. The recipe further indicates action pointers in the lookup table entry that are specific to direction. The action pointers point to an address in an action table that contains instructions for actions that are applied to the packet during switching based on the packet's direction.

Abstract: Disclosed is a mechanism for maintaining a single lookup table entry for symmetric/bidirectional flows. Multiple recipes are stored for each flow. A recipe is employed to select address information from an incoming packet header based on the packet's direction. The address information and an index are employed to generate a lookup key to find the single lookup table entry with the pertinent switching information. The recipe further indicates action pointers in the lookup table entry that are specific to direction. The action pointers point to an address in an action table that contains instructions for actions that are applied to the packet during switching based on the packet's direction.

Abstract: Technologies for flexible tree-based lookups include an network device that receives a network packet. The network device classifies the network packet to determine a packet type and extracts multiple fields from the network packet to generate a field vector. The fields are selected based on the packet type. The field vector includes words that are associated with the fields. The network device builds a tree representation of the field vector. The tree representation includes a leaf node corresponding to each word of the field vector and one or more root nodes. The network device executes an iterative lookup over the tree representation and, if matching, may perform an action associated with the iterative lookup. To execute the lookup, the network device may determine whether a search key for each node exactly matches a search rule, up to a root node. Other embodiments are described and claimed.

Abstract: A network switch circuit associated with a communication network is disclosed. The network switch circuit comprises a switching circuit configured to receive a switch configuration request comprising a configuration command comprising information on a switching rule associated with the network switch circuit; and a configuration template comprising a real packet header comprising real values for one or more fields required for the execution of the switching rule. In some embodiments, the configuration template is indicative of a real network data packet format. In some embodiments, the switching circuit is further configured to process the switch configuration request, in order to apply the switching rule to an incoming network data packet.

Abstract: Disclosed is a mechanism for maintaining a single lookup table entry for symmetric/bidirectional flows. Multiple recipes are stored for each flow. A recipe is employed to select address information from an incoming packet header based on the packet's direction. The address information and an index are employed to generate a lookup key to find the single lookup table entry with the pertinent switching information. The recipe further indicates action pointers in the lookup table entry that are specific to direction. The action pointers point to an address in an action table that contains instructions for actions that are applied to the packet during switching based on the packet's direction.