[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230124104511.293938-1-steen.hegelund@microchip.com>
Date: Tue, 24 Jan 2023 11:45:03 +0100
From: Steen Hegelund <steen.hegelund@...rochip.com>
To: "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
CC: Steen Hegelund <steen.hegelund@...rochip.com>,
<UNGLinuxDriver@...rochip.com>,
Randy Dunlap <rdunlap@...radead.org>,
"Casper Andersson" <casper.casan@...il.com>,
Russell King <rmk+kernel@...linux.org.uk>,
Wan Jiabing <wanjiabing@...o.com>,
"Nathan Huckleberry" <nhuck@...gle.com>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
"Steen Hegelund" <Steen.Hegelund@...rochip.com>,
Daniel Machon <daniel.machon@...rochip.com>,
Horatiu Vultur <horatiu.vultur@...rochip.com>,
Lars Povlsen <lars.povlsen@...rochip.com>,
Dan Carpenter <error27@...il.com>,
Michael Walle <michael@...le.cc>
Subject: [PATCH net-next v2 0/8] Adding Sparx5 IS0 VCAP support
This provides the Ingress Stage 0 (IS0) VCAP (Versatile Content-Aware
Processor) support for the Sparx5 platform.
The IS0 VCAP (also known in the datasheet as CLM) is a classifier VCAP that
mainly extracts frame information to metadata that follows the frame in the
Sparx5 processing flow all the way to the egress port.
The IS0 VCAP has 4 lookups and they are accessible with a TC chain id:
- chain 1000000: IS0 Lookup 0
- chain 1100000: IS0 Lookup 1
- chain 1200000: IS0 Lookup 2
- chain 1300000: IS0 Lookup 3
- chain 1400000: IS0 Lookup 4
- chain 1500000: IS0 Lookup 5
Each of these lookups have their own port keyset configuration that decides
which keys will be used for matching on which traffic type.
The IS0 VCAP has these traffic classifications:
- IPv4 frames
- IPv6 frames
- Unicast MPLS frames (ethertype = 0x8847)
- Multicast MPLS frames (ethertype = 0x8847)
- Other frame types than MPLS, IPv4 and IPv6
The IS0 VCAP has an action that allows setting the value of a PAG (Policy
Association Group) key field in the frame metadata, and this can be used
for matching in an IS2 VCAP rule.
This allow rules in the IS0 VCAP to be linked to rules in the IS2 VCAP.
The linking is exposed by using the TC "goto chain" action with an offset
from the IS2 chain ids.
As an example a "goto chain 8000001" will use a PAG value of 1 to chain to
a rule in IS2 Lookup 0.
Version History:
================
v2 Added corrections suggested by Dan Carpenter.
v1 Initial version
Steen Hegelund (8):
net: microchip: sparx5: Add IS0 VCAP model and updated KUNIT VCAP
model
net: microchip: sparx5: Add IS0 VCAP keyset configuration for Sparx5
net: microchip: sparx5: Add actionset type id information to rule
net: microchip: sparx5: Add TC support for IS0 VCAP
net: microchip: sparx5: Add TC filter chaining support for IS0 and IS2
VCAPs
net: microchip: sparx5: Add automatic selection of VCAP rule actionset
net: microchip: sparx5: Add support for IS0 VCAP ethernet protocol
types
net: microchip: sparx5: Add support for IS0 VCAP CVLAN TC keys
.../microchip/sparx5/sparx5_main_regs.h | 64 +-
.../microchip/sparx5/sparx5_tc_flower.c | 227 +-
.../microchip/sparx5/sparx5_vcap_ag_api.c | 1110 ++++++++-
.../microchip/sparx5/sparx5_vcap_debugfs.c | 131 +-
.../microchip/sparx5/sparx5_vcap_impl.c | 401 +++-
.../microchip/sparx5/sparx5_vcap_impl.h | 61 +
.../net/ethernet/microchip/vcap/vcap_ag_api.h | 336 +--
.../net/ethernet/microchip/vcap/vcap_api.c | 184 +-
.../net/ethernet/microchip/vcap/vcap_api.h | 7 +
.../ethernet/microchip/vcap/vcap_api_client.h | 2 +
.../ethernet/microchip/vcap/vcap_api_kunit.c | 2 +-
.../microchip/vcap/vcap_model_kunit.c | 1994 ++---------------
12 files changed, 2360 insertions(+), 2159 deletions(-)
--
2.39.1
Powered by blists - more mailing lists