From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
cjubran@nvidia.com, cratiu@nvidia.com, gal@nvidia.com,
leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, mbloch@nvidia.com, moshe@nvidia.com,
ohartoov@nvidia.com, phaddad@nvidia.com, saeedm@nvidia.com,
shayd@nvidia.com, udar@nvidia.com
Subject: Re: [PATCH net-next V2 00/10] net/mlx5: LAG, preparations for LAG over VFs/SFs
Date: Fri, 20 Nov 2026 00:40:09 +0000 [thread overview]
Message-ID: <179513520953.3950719.4715041705999451652.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116103010.1129666-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Nov 2026 12:30:00 +0200 you wrote:
> Hi,
>
> This series by Shay is the first part of enabling a LAG over functions
> that do not represent a physical port - a "virtual LAG" (virt LAG) of
> VFs or SFs acting as nested e-switch managers. New FW lets a VF/SF front
> the physical uplinks through a multi-uplink e-switch; such a function
> reports num_lag_ports < 2 and drives port selection via the e-switch
> (port_select_eswitch) rather than the HW port-selection flow table. A
> virt LAG is therefore a software-managed, shared-FDB MPESW LAG: the
> driver builds the LAG demux and vport-LAG in software.
>
> [...]
Here is the summary with links:
- [net-next,V2,01/10] net/mlx5: Distinguish VFs/SFs in the SW system image GUID for LAG grouping
https://git.kernel.org/netdev/net-next/c/c25049685e16
- [net-next,V2,02/10] net/mlx5: LAG, select the MPESW master from the live member snapshot
https://git.kernel.org/netdev/net-next/c/2bfcb28b10e8
- [net-next,V2,03/10] net/mlx5: LAG, skip phys LAG prerequisites for a virt LAG
https://git.kernel.org/netdev/net-next/c/a2d029ad50e2
- [net-next,V2,04/10] net/mlx5: LAG, treat virt LAG as a software managed LAG
https://git.kernel.org/netdev/net-next/c/b03cb2fdbbdb
- [net-next,V2,05/10] net/mlx5: LAG, decouple iteration end-of-walk from MLX5_MAX_PORTS
https://git.kernel.org/netdev/net-next/c/4eef67c32a7b
- [net-next,V2,06/10] net/mlx5: LAG, rename PF naming to fn
https://git.kernel.org/netdev/net-next/c/1e6086bcd491
- [net-next,V2,07/10] net/mlx5: LAG, resolve affinity indices only in queue-affinity mode
https://git.kernel.org/netdev/net-next/c/26da1e56cef9
- [net-next,V2,08/10] net/mlx5: LAG: replace fixed MLX5_MAX_PORTS arrays with dynamic allocation
https://git.kernel.org/netdev/net-next/c/b7826ed4d0b5
- [net-next,V2,09/10] net/mlx5: LAG, drop MLX5_MAX_PORTS scratch array from device rescan
https://git.kernel.org/netdev/net-next/c/0da8bb5da54f
- [net-next,V2,10/10] net/mlx5: LAG, do not add a device to an already-active virt LAG
https://git.kernel.org/netdev/net-next/c/5830905813d0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-20 0:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 10:30 [PATCH net-next V2 00/10] net/mlx5: LAG, preparations for LAG over VFs/SFs Tariq Toukan
2026-11-16 10:30 ` [PATCH net-next V2 01/10] net/mlx5: Distinguish VFs/SFs in the SW system image GUID for LAG grouping Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-18 10:31 ` netdev-bot+sashiko
2026-11-19 7:40 ` Shay Drory
2026-11-16 10:30 ` [PATCH net-next V2 02/10] net/mlx5: LAG, select the MPESW master from the live member snapshot Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-16 10:30 ` [PATCH net-next V2 03/10] net/mlx5: LAG, skip phys LAG prerequisites for a virt LAG Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-16 10:30 ` [PATCH net-next V2 04/10] net/mlx5: LAG, treat virt LAG as a software managed LAG Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-16 10:30 ` [PATCH net-next V2 05/10] net/mlx5: LAG, decouple iteration end-of-walk from MLX5_MAX_PORTS Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-18 10:31 ` netdev-bot+sashiko
2026-11-19 8:10 ` Shay Drory
2026-11-16 10:30 ` [PATCH net-next V2 06/10] net/mlx5: LAG, rename PF naming to fn Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-18 10:31 ` netdev-bot+sashiko
2026-11-16 10:30 ` [PATCH net-next V2 07/10] net/mlx5: LAG, resolve affinity indices only in queue-affinity mode Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-16 10:30 ` [PATCH net-next V2 08/10] net/mlx5: LAG: replace fixed MLX5_MAX_PORTS arrays with dynamic allocation Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-18 10:31 ` netdev-bot+sashiko
2026-11-19 8:20 ` Shay Drory
2026-11-16 10:30 ` [PATCH net-next V2 09/10] net/mlx5: LAG, drop MLX5_MAX_PORTS scratch array from device rescan Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-18 10:31 ` netdev-bot+sashiko
2026-11-19 8:40 ` Shay Drory
2026-11-16 10:30 ` [PATCH net-next V2 10/10] net/mlx5: LAG, do not add a device to an already-active virt LAG Tariq Toukan
2026-11-17 10:36 ` sashiko-bot
2026-11-18 10:32 ` netdev-bot+sashiko
2026-11-19 8:58 ` Shay Drory
2026-11-20 0:40 ` patchwork-bot+netdevbpf [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=179513520953.3950719.4715041705999451652.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=phaddad@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=udar@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 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.