netdev - Re: [PATCH net-next 00/10] mlxsw: Add port range matching support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ZLJdvjzDU+DvIQah@corigine.com>
Date: Sat, 15 Jul 2023 09:50:06 +0100
From: Simon Horman <simon.horman@...igine.com>
To: Petr Machata <petrm@...dia.com>
Cc: "David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	netdev@...r.kernel.org, Ido Schimmel <idosch@...dia.com>,
	mlxsw@...dia.com
Subject: Re: [PATCH net-next 00/10] mlxsw: Add port range matching support

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@...igine.com>