summaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2019-04-15 15:45:36 -0700
committerDavid S. Miller <davem@davemloft.net>2019-04-15 15:45:36 -0700
commitb6ed55cb721c13497c3cddd6caee46a7f92c4e7b (patch)
treeafc33722607e7a62e09133bd2619e4d16c2b0fbf /init
parent47a1a225ab35038ac158494fac87b4b7b2e59d58 (diff)
parent8af56f40e53b102a1f7ef5cd2b057cd6db776d6e (diff)
Merge branch 'nfp-Flower-flow-merging'
Simon Horman says: ==================== nfp: Flower flow merging John Hurley says, These patches deal with 'implicit recirculation' on the NFP. This is a firmware feature whereby a packet egresses to an 'internal' port meaning that it will recirculate back to the header extract phase with the 'internal' port now marked as its ingress port. This internal port can then be matched on by another rule. This process simulates how OvS datapath outputs to an internal port. The FW traces the packet's recirculation route and sends a 'merge hint' to the driver telling it which flows it matched against. The driver can then decide if these flows can be merged to a single rule and offloaded. The patches deal with the following issues: - assigning/freeing IDs to/from each of these new internal ports - offloading rules that match on internal ports - offloading neighbour table entries whose egress port is internal - handling fallback traffic with an internal port as ingress - using merge hints to create 'faster path' flows and tracking stats etc. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions