From: Simon Horman <simon.horman@corigine.com>
To: Petr Machata <petrm@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Ido Schimmel <idosch@nvidia.com>,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next 00/10] mlxsw: Add port range matching support
Date: Sat, 15 Jul 2023 09:50:06 +0100 [thread overview]
Message-ID: <ZLJdvjzDU+DvIQah@corigine.com> (raw)
In-Reply-To: <cover.1689092769.git.petrm@nvidia.com>
On Tue, Jul 11, 2023 at 06:43:53PM +0200, Petr Machata wrote:
> Ido Schimmel writes:
>
> Add port range matching support in mlxsw as part of tc-flower offload.
>
> Patches #1-#7 gradually add port range matching support in mlxsw. See
> patch #3 to understand how port range matching is implemented in the
> device.
>
> Patches #8-#10 add selftests.
>
> Ido Schimmel (10):
> mlxsw: reg: Add Policy-Engine Port Range Register
> mlxsw: resource: Add resource identifier for port range registers
> mlxsw: spectrum_port_range: Add port range core
> mlxsw: spectrum_port_range: Add devlink resource support
> mlxsw: spectrum_acl: Add port range key element
> mlxsw: spectrum_acl: Pass main driver structure to
> mlxsw_sp_acl_rulei_destroy()
> mlxsw: spectrum_flower: Add ability to match on port ranges
> selftests: mlxsw: Add scale test for port ranges
> selftests: mlxsw: Test port range registers' occupancy
> selftests: forwarding: Add test cases for flower port range matching
Reviewed-by: Simon Horman <simon.horman@corigine.com>
prev parent reply other threads:[~2023-07-15 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 16:43 [PATCH net-next 00/10] mlxsw: Add port range matching support Petr Machata
2023-07-11 16:43 ` [PATCH net-next 01/10] mlxsw: reg: Add Policy-Engine Port Range Register Petr Machata
2023-07-11 16:43 ` [PATCH net-next 02/10] mlxsw: resource: Add resource identifier for port range registers Petr Machata
2023-07-11 16:43 ` [PATCH net-next 03/10] mlxsw: spectrum_port_range: Add port range core Petr Machata
2023-07-11 16:43 ` [PATCH net-next 04/10] mlxsw: spectrum_port_range: Add devlink resource support Petr Machata
2023-07-11 16:43 ` [PATCH net-next 05/10] mlxsw: spectrum_acl: Add port range key element Petr Machata
2023-07-11 16:43 ` [PATCH net-next 06/10] mlxsw: spectrum_acl: Pass main driver structure to mlxsw_sp_acl_rulei_destroy() Petr Machata
2023-07-11 16:44 ` [PATCH net-next 07/10] mlxsw: spectrum_flower: Add ability to match on port ranges Petr Machata
2023-07-11 16:44 ` [PATCH net-next 08/10] selftests: mlxsw: Add scale test for " Petr Machata
2023-07-11 16:44 ` [PATCH net-next 09/10] selftests: mlxsw: Test port range registers' occupancy Petr Machata
2023-07-11 16:44 ` [PATCH net-next 10/10] selftests: forwarding: Add test cases for flower port range matching Petr Machata
2023-07-13 0:10 ` [PATCH net-next 00/10] mlxsw: Add port range matching support patchwork-bot+netdevbpf
2023-07-15 8:50 ` Simon Horman [this message]
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=ZLJdvjzDU+DvIQah@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).