Managed Forwarding Element With Conjunctive Match Flow Entries
US-2017034082-A1 · Feb 2, 2017 · US
US9825862B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9825862-B2 |
| Application number | US-201514836850-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 26, 2015 |
| Priority date | Aug 26, 2015 |
| Publication date | Nov 21, 2017 |
| Grant date | Nov 21, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Some embodiments provide a method for processing a packet for a pipeline of a hardware switch. The pipeline, in some embodiments, includes several different stages that match against packet header fields and modify packet header fields. The method receives a packet that includes a set of packet headers. The method then populates, for each packet header in the set of packet headers, (i) a first set of registers with packet header field values of the packet header that are used in the pipeline, and (ii) a second set of registers with packet header field values of the packet header that are not used in the pipeline.
Opening claim text (preview).
What is claimed is: 1. A method for processing a packet for a pipeline of a hardware switch, the pipeline comprising a plurality of stages that match against packet header fields and modify packet header fields, the method comprising: receiving a packet comprising a set of packet headers; for each packet header in the set of packet headers: populating a first set of registers with packet header field values of the packet header that are used in the pipeline; and populating a second set of registers with packet header field values of the packet header that are not used in the pipeline. 2. The method of claim 1 , wherein the pipeline comprises one of an ingress pipeline and an egress pipeline of the hardware switch. 3. The method of claim 1 , wherein the pipeline comprises a parser, a match-action unit (MAU), and a deparser, wherein the first set of registers is delivered to the MAU for further processing and the second set of registers is delivered directly to the deparser without being processed by the MAU. 4. The method of claim 3 , wherein the MAU comprises a set of match-action stages, each of which comprises a set of match tables against which at least a subset of the packet header field values stored in the first set of registers is matched. 5. The method of claim 4 , wherein each of the match-action stages of the MAU further comprises a set of action entries and an action engine for performing a set of actions specified by an action entry that corresponds to a match entry of the set of match tables of the match-action stage. 6. The method of claim 5 , wherein the set of actions comprises modifying one or more of the header field values stored in the first set of registers. 7. The method of claim 1 , wherein for a particular packet, only a first subset of the packet header field values stored in the first set of registers are used in the pipeline. 8. The method of claim 7 , wherein a second subset of the packet header field values stored in the first set of registers are not used for the particular packet, but used for other packets. 9. The method of claim 7 , wherein a particular packet header field value is used in the pipeline when either (i) a match entry matches against the packet header field value or (ii) an action entry modifies the packet header field value. 10. The method of claim 1 , wherein the first set of registers are populated with values of different packet header fields for a first packet than for a second packet based on the values of a particular packet header field in the packet headers of the first and second packets. 11. The method of claim 10 , wherein the particular packet header field is the EtherType field of Ethernet headers. 12. The method of claim 1 further comprising, for each of at least a subset of the packet headers, determining a format of a next packet header by matching a value of a particular packet header field of the packet header against a set of TCAM entries. 13. A non-transitory machine readable medium storing a program which when executed by at least one processing unit processes a packet for a pipeline of a hardware switch, the pipeline comprising a plurality of stages that match against packet header fields and modify packet header fields, the program comprising sets of instructions for: receiving a packet comprising a set of packet headers; for each packet header in the set of packet headers: populating a first set of registers with packet header field values of the packet header that are used in the pipeline; and populating a second set of registers with packet header field values of the packet header that are not used in the pipeline. 14. The machine readable medium of claim 13 , wherein the pipeline comprises one of an ingress pipeline and an egress pipeline of the hardware switch. 15. The machine readable medium of claim 13 , wherein the pipeline comprises a parser, a match-action unit (MAU), and a deparser, wherein the program further comprises sets of instructions for: delivering the first set of registers to the MAU for further processing; and delivering the second set of registers directly to the deparser without having the MAU process the second set. 16. The machine readable medium of claim 15 , wherein the MAU comprises a set of match-action stages, each of which comprises a set of match tables against which at least a subset of the packet header field values stored in the first set of registers is matched. 17. The machine readable medium of claim 16 , wherein each of the match-action stages of the MAU further comprises a set of action entries and an action engine for performing a set of actions specified by an action entry that corresponds to a match entry of the set of match tables of the match-action stage. 18. The machine readable medium of claim 17 , wherein the set of actions comprises modifying one or more of the header field values stored in the first set of registers. 19. The machine readable medium of claim 13 , wherein for a particular packet, only a first subset of the packet header field values stored in the first set of registers are used in the pipeline. 20. The machine readable medium of claim 13 , wherein the program further comprises, for each of at least a subset of the packet headers, determining a format of a next packet header by matching a value of a particular packet header field of the packet header against a set of TCAM entries.
Organization of routing tables · CPC title
Parsing or analysis of headers · CPC title
using an overlay routing layer · CPC title
using crossbar or matrix · CPC title
Centralised routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.