[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251109102224.GI15456@unreal>
Date: Sun, 9 Nov 2025 12:22:24 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Edward Srouji <edwards@...dia.com>
Cc: Saeed Mahameed <saeedm@...dia.com>, Tariq Toukan <tariqt@...dia.com>,
Mark Bloch <mbloch@...dia.com>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Jason Gunthorpe <jgg@...pe.ca>, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
Patrisious Haddad <phaddad@...dia.com>
Subject: Re: [PATCH rdma-next 0/7] Add other eswitch support
On Wed, Oct 29, 2025 at 05:42:52PM +0200, Edward Srouji wrote:
> From: Patrisious Haddad <phaddad@...dia.com>
>
> From Patrisious:
> When the device in switchdev mode, the RDMA device manages all the
> vports which belong to its representors, which can lead to a situation
> where the PF that is used to manage the RDMA device isn't the native PF
> of some of the vports it manages.
>
> Add infrastructure to allow the master PF to manage all the hardware
> resources for the vports under its management.
> Whereas currently the only such resource is RDMA TRANSPORT steering
> domains.
>
> That is done by adding new FW argument other_eswitch which is passed by
> the driver to the FW to allow the master PF to properly manage vports
> belonging to other native PF.
>
> ---
> Patrisious Haddad (7):
> net/mlx5: Add OTHER_ESWITCH HW capabilities
> net/mlx5: fs, Add other_eswitch support for steering tables
> net/mlx5: fs, set non default device per namespace
> RDMA/mlx5: Change default device for LAG slaves in RDMA TRANSPORT namespaces
> RDMA/mlx5: Add other_eswitch support for devx destruction
> RDMA/mlx5: Refactor _get_prio() function
> RDMA/mlx5: Add other eswitch support to userspace tables
>
Thanks, applied.
Powered by blists - more mailing lists