All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	UNGLinuxDriver@microchip.com,
	Randy Dunlap <rdunlap@infradead.org>,
	Casper Andersson <casper.casan@gmail.com>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Wan Jiabing <wanjiabing@vivo.com>,
	Nathan Huckleberry <nhuck@google.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Daniel Machon <daniel.machon@microchip.com>,
	Horatiu Vultur <horatiu.vultur@microchip.com>,
	Lars Povlsen <lars.povlsen@microchip.com>,
	Michael Walle <michael@walle.cc>
Subject: Re: [PATCH net-next v2 0/8] Adding Sparx5 IS0 VCAP support
Date: Tue, 24 Jan 2023 13:57:45 +0300	[thread overview]
Message-ID: <Y8+5qSgbSupca1bu@kadam> (raw)
In-Reply-To: <20230124104511.293938-1-steen.hegelund@microchip.com>

On Tue, Jan 24, 2023 at 11:45:03AM +0100, Steen Hegelund wrote:
> 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.

Thanks!

regards,
dan carpenter


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	UNGLinuxDriver@microchip.com,
	Randy Dunlap <rdunlap@infradead.org>,
	Casper Andersson <casper.casan@gmail.com>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Wan Jiabing <wanjiabing@vivo.com>,
	Nathan Huckleberry <nhuck@google.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Daniel Machon <daniel.machon@microchip.com>,
	Horatiu Vultur <horatiu.vultur@microchip.com>,
	Lars Povlsen <lars.povlsen@microchip.com>,
	Michael Walle <michael@walle.cc>
Subject: Re: [PATCH net-next v2 0/8] Adding Sparx5 IS0 VCAP support
Date: Tue, 24 Jan 2023 13:57:45 +0300	[thread overview]
Message-ID: <Y8+5qSgbSupca1bu@kadam> (raw)
In-Reply-To: <20230124104511.293938-1-steen.hegelund@microchip.com>

On Tue, Jan 24, 2023 at 11:45:03AM +0100, Steen Hegelund wrote:
> 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.

Thanks!

regards,
dan carpenter


  parent reply	other threads:[~2023-01-24 10:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 10:45 [PATCH net-next v2 0/8] Adding Sparx5 IS0 VCAP support Steen Hegelund
2023-01-24 10:45 ` Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 1/8] net: microchip: sparx5: Add IS0 VCAP model and updated KUNIT VCAP model Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 2/8] net: microchip: sparx5: Add IS0 VCAP keyset configuration for Sparx5 Steen Hegelund
2023-01-24 10:45   ` Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 3/8] net: microchip: sparx5: Add actionset type id information to rule Steen Hegelund
2023-01-24 10:45   ` Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 4/8] net: microchip: sparx5: Add TC support for IS0 VCAP Steen Hegelund
2023-01-24 10:45   ` Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 5/8] net: microchip: sparx5: Add TC filter chaining support for IS0 and IS2 VCAPs Steen Hegelund
2023-01-24 10:45   ` Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 6/8] net: microchip: sparx5: Add automatic selection of VCAP rule actionset Steen Hegelund
2023-01-24 10:45   ` Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 7/8] net: microchip: sparx5: Add support for IS0 VCAP ethernet protocol types Steen Hegelund
2023-01-24 10:45   ` Steen Hegelund
2023-01-24 10:45 ` [PATCH net-next v2 8/8] net: microchip: sparx5: Add support for IS0 VCAP CVLAN TC keys Steen Hegelund
2023-01-24 10:45   ` Steen Hegelund
2023-01-24 10:57 ` Dan Carpenter [this message]
2023-01-24 10:57   ` [PATCH net-next v2 0/8] Adding Sparx5 IS0 VCAP support Dan Carpenter
2023-01-26  9:30 ` patchwork-bot+netdevbpf
2023-01-26  9:30   ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y8+5qSgbSupca1bu@kadam \
    --to=error27@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=casper.casan@gmail.com \
    --cc=daniel.machon@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=lars.povlsen@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=netdev@vger.kernel.org \
    --cc=nhuck@google.com \
    --cc=pabeni@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=steen.hegelund@microchip.com \
    --cc=wanjiabing@vivo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.