diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2023-02-16 10:59:51 +0300 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2023-02-16 10:59:51 +0300 |
| commit | 8fdf6659974d697ef09acd216ffff34706a1b83a (patch) | |
| tree | 268cd50f36189883faf7192c37ea51a352ab22cc /net | |
| parent | 72bc7f163179cb0b39e1a18dbf69e175267ce500 (diff) | |
| parent | ebf44ded76e92e0812e0e4a2acd20c7f86550e2c (diff) | |
| download | linux-8fdf6659974d697ef09acd216ffff34706a1b83a.tar.xz | |
Merge branch 'adding-sparx5-es0-vcap-support'
Steen Hegelund says:
====================
Adding Sparx5 ES0 VCAP support
This provides the Egress Stage 0 (ES0) VCAP (Versatile Content-Aware
Processor) support for the Sparx5 platform.
The ES0 VCAP is an Egress Access Control VCAP that uses frame keyfields and
previously classified keyfields to add, rewrite or remove VLAN tags on the
egress frames, and is therefore often referred to as the rewriter.
The ES0 VCAP also supports trapping frames to the host.
The ES0 VCAP has 1 lookup accessible with this chain id:
- chain 10000000: ES0 Lookup 0
The ES0 VCAP does not do traffic classification to select a keyset, but it
does have two keysets that can be used on all traffic. For now only the
ISDX keyset is used.
The ES0 VCAP can match on an ISDX key (Ingress Service Index) as one of the
frame metadata keyfields, similar to the ES2 VCAP.
The ES0 VCAP uses external counters in the XQS (statistics) group.
====================
Link: https://lore.kernel.org/r/20230214104049.1553059-1-steen.hegelund@microchip.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions