diff options
| author |   John Hurley <john.hurley@netronome.com> | 2019-08-04 16:09:07 +0100 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2019-08-06 14:24:21 -0700 |
| commit | 4b10c53d81fd1350a5510f3038f52b5db9c953e0 (patch) | |
| tree | 5fb5e52976540c11b935fbbd16c972317f15fa67 /LICENSES | |
| parent | net: sched: add ingress mirred action to hardware IR (diff) | |
| download | linux-dev-4b10c53d81fd1350a5510f3038f52b5db9c953e0.tar.xz linux-dev-4b10c53d81fd1350a5510f3038f52b5db9c953e0.zip | |
nfp: flower: push vlan after tunnel in merge
NFP allows the merging of 2 flows together into a single offloaded flow.
In the kernel datapath the packet must match 1 flow, impliment its
actions, recirculate, match the 2nd flow and also impliment its actions.
Merging creates a single flow with all actions from the 2 original flows.
Firmware impliments a tunnel header push as the packet is about to egress
the card. Therefore, if the first merge rule candiate pushes a tunnel,
then the second rule can only have an egress action for a valid merge to
occur (or else the action ordering will be incorrect). This prevents the
pushing of a tunnel header followed by the pushing of a vlan header.
In order to support this behaviour, firmware allows VLAN information to
be encoded in the tunnel push action. If this is non zero then the fw will
push a VLAN after the tunnel header push meaning that 2 such flows with
these actions can be merged (with action order being maintained).
Support tunnel in VLAN pushes by encoding VLAN information in the tunnel
push action of any merge flow requiring this.
Signed-off-by: John Hurley <john.hurley@netronome.com>
Reviewed-by: Simon Horman <simon.horman@netronome.com>
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'LICENSES')
0 files changed, 0 insertions, 0 deletions