diff options
author | David S. Miller <davem@davemloft.net> | 2023-01-30 10:36:23 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2023-01-30 10:36:23 +0300 |
commit | 166a1a5a12b056a389b8dc529033cafaa290ca7c (patch) | |
tree | 36dacc26d18d83c1a5d40f956c8c84bcf0456234 /net/devlink | |
parent | 5dd3beba220224bd3539243d68d6bf322478d5a8 (diff) | |
parent | 1f741f0011608ddbf4761c9bb8e2c4ecf6d6dedb (diff) | |
download | linux-166a1a5a12b056a389b8dc529033cafaa290ca7c.tar.xz |
Merge branch 'sparx5-ES2-VCAP-support'
Steen Hegelund says:
====================
Adding Sparx5 ES2 VCAP support
This provides the Egress Stage 2 (ES2) VCAP (Versatile Content-Aware
Processor) support for the Sparx5 platform.
The ES2 VCAP is an Egress Access Control VCAP that uses frame keyfields and
previously classified keyfields to apply e.g. policing, trapping or
mirroring to frames.
The ES2 VCAP has 2 lookups and they are accessible with a TC chain id:
- chain 20000000: ES2 Lookup 0
- chain 20100000: ES2 Lookup 1
As the other Sparx5 VCAPs the ES2 VCAP has its own lookup/port keyset
configuration that decides which keys will be used for matching on which
traffic type.
The ES2 VCAP has these traffic classifications:
- IPv4 frames
- IPv6 frames
- Other frames
The ES2 VCAP can match on an ISDX key (Ingress Service Index) as one of the
frame metadata keyfields. The IS0 VCAP can update this key using its
actions, and this allows a IS0 VCAP rule to be linked to an ES2 rule.
This is similar to how the IS0 VCAP and the IS2 VCAP use the PAG
(Policy Association Group) keyfield to link rules.
From user space this is exposed via "chain offsets", so an IS0 rule with a
"goto chain 20000015" action will use an ISDX key value of 15 to link to a
rule in the ES2 VCAP attached to the same chain id.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/devlink')
0 files changed, 0 insertions, 0 deletions