US 10,476,747 B1Granted

Loading a flow tracking autolearning match table

AssigneeNetronome Systems, Inc.

InventorJohann H. Tönsing

Life of this patent

Estimating the term…

Loading patent…

Abstract

A networking device includes: 1) a first processor that includes a match table, and 2) a second processor that includes both a Flow Tracking Autolearning Match Table (FTAMT) as well as a synchronized match table. A set of multiple entries stored in the synchronized match table is synchronized with a corresponding set of multiple entries in the match table on the first processor. The FTAMT, for a first packet of the flow, generates a Flow Identifier (ID) and stores the flow ID as part of a new entry for the flow. The match of a packet to one of the synchronized entries in the synchronized match table causes an action identifier to be recorded in the new entry in the FTAMT. A subsequent packet of the flow results in a hit in the FTAMT and results in the previously recorded action being applied to the subsequent packet.

Claims20

Dependent claims

A networking device, comprising:

a first processor comprising:
a match table that stores a plurality of entries;
and
a second processor comprising:
a synchronized match table that stores a plurality of entries, wherein the plurality of entries stored in the synchronized match table is synchronized with a corresponding plurality of entries stored in the match table of the first processor;
and
a flow tracking autolearning match table, wherein a match of a first packet to one of the synchronized entries in the synchronized match table causes an action to be recorded in the flow tracking autolearning match table in association with a flow of the first packet, and wherein the action is recorded without the first processor being first alerted of the recording, and without the first processor first receiving the first packet from the second processor, and without the first processor instructing the flow tracking autolearning match table to record the action, wherein the flow tracking autolearning match table, for the first packet of the flow, generates a Flow Identifier (Flow ID) and stores the Flow ID as part of an entry for the flow and directs the first packet to the synchronized match table for possible matching, and wherein a subsequent packet of the flow results in a hit in the flow tracking autolearning match table and results in the previously recorded action being applied to the subsequent packet.

4 more elements

A networking device, comprising:

a host comprising:
a first processor;
and
a memory that stores a kernel mode match table, wherein the kernel mode match table stores a plurality of entries;
and
a Network Interface Device (NID) that is coupled to the host by a bus, wherein the NID comprises:
a second processor;
and
an amount of memory, wherein the amount of memory stores:
a synchronized match table, wherein a plurality of synchronized entries stored in the synchronized match table is synchronized with a corresponding plurality of entries stored in the kernel mode match table of the host;
and
a flow tracking autolearning match table, wherein a match of a first packet to one of the synchronized entries in the synchronized match table causes an action identifier to be recorded in the flow tracking autolearning table in association with a flow of the first packet, wherein a Flow Identifier (Flow ID) is generated for the first packet of the flow and is stored as part of an entry for the flow in the flow tracking autolearning match table, and wherein the synchronized match table is then consulted for possible matching to the first packet, and wherein a subsequent packet of the flow results in a hit in the flow tracking autolearning match table and results in an action identified by the previously recorded action identifier being applied to the subsequent packet.

9 more elements

A method involving a host and Network Interface Device (NID), wherein the NID is coupled to the host via a bus, the method comprising:

(a) maintaining a kernel mode match table on the host;
(b) maintaining a synchronized match table on the NID;
(c) synchronizing the synchronized match table to the kernel mode match table;
(d) receiving a first packet of a flow onto the NID;
(e) generating a Flow Identifier (Flow ID) for the flow, wherein the generating is performed on the NID;
(f) loading an entry for the flow into a flow tracking autolearning match table, wherein the entry includes the Flow ID, wherein the flow tracking autolearning match table is a part of the NID;
(g) attempting a lookup of the first packet in the synchronized match table thereby identifying a matching synchronized entry, wherein the matching synchronized entry of the synchronized match table includes an action identifier;
and
(h) recording the action identifier in the entry in the flow tracking autolearning match table, wherein (a) is performed by the host and wherein (b) through (h) are performed by the NID.

6 more elements

Dependencies are inferred from the claim text.