From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
agoldberger@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, saeedm@nvidia.com, shayd@nvidia.com
Subject: Re: [PATCH net-next 00/13] net/mlx5: Preparations for nested E-switch
Date: Tue, 29 Sep 2026 00:20:07 +0000 [thread overview]
Message-ID: <179064120790.188287.14668641337564861331.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260923103830.1183-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Sep 2026 13:38:17 +0300 you wrote:
> Hi,
>
> This series by Shay has two intertwined goals. The first is to remove
> the compile-time MLX5_MAX_PORTS sizing from the LAG and eswitch/TC
> datapaths so that structures scale with the actual number of ports/peers
> rather than a fixed maximum. The second is a set of small,
> self-contained fixes that prepare the eswitch and LAG code for a VF/SF
> acting as a nested e-switch manager - a mode new FW will allow, where a
> VF/SF has its own eswitch and the VFs/SFs can be grouped by MPESW.
>
> [...]
Here is the summary with links:
- [net-next,01/13] net/mlx5e: Assign a random MAC to any netdev with a zero MAC address
https://git.kernel.org/netdev/net-next/c/cfda5de64053
- [net-next,02/13] net/mlx5: E-switch, do not leave an unpaired devcom registered
https://git.kernel.org/netdev/net-next/c/11dac22ca063
- [net-next,03/13] net/mlx5: LAG, allocate v2p_map dynamically
https://git.kernel.org/netdev/net-next/c/d9f3227f673b
- [net-next,04/13] net/mlx5: LAG, allocate port-indexed scratch buffers dynamically
https://git.kernel.org/netdev/net-next/c/4138820bddda
- [net-next,05/13] net/mlx5: LAG, drop per-port scratch array in drop-rule setup
https://git.kernel.org/netdev/net-next/c/fbc4f422c5b8
- [net-next,06/13] net/mlx5: LAG, size debugfs buffers by port count
https://git.kernel.org/netdev/net-next/c/6c244dd5ba6b
- [net-next,07/13] net/mlx5e: TC, anchor peer-flow reverse index on the duplicated flow
https://git.kernel.org/netdev/net-next/c/675956237b38
- [net-next,08/13] net/mlx5e: TC, track peer flows in a vhca_id xarray
https://git.kernel.org/netdev/net-next/c/9d608a40c2d4
- [net-next,09/13] net/mlx5: E-switch, derive manager vport from device capability
https://git.kernel.org/netdev/net-next/c/d451adde0203
- [net-next,10/13] net/mlx5: LAG, don't print port mapping to debugfs in MPESW mode
https://git.kernel.org/netdev/net-next/c/c51ea6db00e6
- [net-next,11/13] net/mlx5: LAG, drop stale esw_shared_ingress_acl gate from shared FDB
https://git.kernel.org/netdev/net-next/c/66b25da0cfed
- [net-next,12/13] net/mlx5: E-switch, correct stale VF/PF wording in esw-allowed comments
https://git.kernel.org/netdev/net-next/c/dd655b1e93c1
- [net-next,13/13] net/mlx5: E-switch, disable host functions for a non PF e-switch manager
https://git.kernel.org/netdev/net-next/c/a5bfbdfebd53
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-09-29 0:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:38 [PATCH net-next 00/13] net/mlx5: Preparations for nested E-switch Tariq Toukan
2026-09-23 10:38 ` [PATCH net-next 01/13] net/mlx5e: Assign a random MAC to any netdev with a zero MAC address Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:45 ` netdev-bot+sashiko
2026-09-23 10:38 ` [PATCH net-next 02/13] net/mlx5: E-switch, do not leave an unpaired devcom registered Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:45 ` netdev-bot+sashiko
2026-09-23 10:38 ` [PATCH net-next 03/13] net/mlx5: LAG, allocate v2p_map dynamically Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:45 ` netdev-bot+sashiko
2026-09-28 14:56 ` Shay Drori
2026-09-23 10:38 ` [PATCH net-next 04/13] net/mlx5: LAG, allocate port-indexed scratch buffers dynamically Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:45 ` netdev-bot+sashiko
2026-09-28 14:57 ` Shay Drori
2026-09-23 10:38 ` [PATCH net-next 05/13] net/mlx5: LAG, drop per-port scratch array in drop-rule setup Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-23 10:38 ` [PATCH net-next 06/13] net/mlx5: LAG, size debugfs buffers by port count Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:45 ` netdev-bot+sashiko
2026-09-23 10:38 ` [PATCH net-next 07/13] net/mlx5e: TC, anchor peer-flow reverse index on the duplicated flow Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:45 ` netdev-bot+sashiko
2026-09-23 10:38 ` [PATCH net-next 08/13] net/mlx5e: TC, track peer flows in a vhca_id xarray Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:46 ` netdev-bot+sashiko
2026-09-23 10:38 ` [PATCH net-next 09/13] net/mlx5: E-switch, derive manager vport from device capability Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-24 17:46 ` netdev-bot+sashiko
2026-09-28 15:13 ` Shay Drori
2026-09-23 10:38 ` [PATCH net-next 10/13] net/mlx5: LAG, don't print port mapping to debugfs in MPESW mode Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-23 10:38 ` [PATCH net-next 11/13] net/mlx5: LAG, drop stale esw_shared_ingress_acl gate from shared FDB Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-23 10:38 ` [PATCH net-next 12/13] net/mlx5: E-switch, correct stale VF/PF wording in esw-allowed comments Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-23 10:38 ` [PATCH net-next 13/13] net/mlx5: E-switch, disable host functions for a non PF e-switch manager Tariq Toukan
2026-09-24 10:41 ` sashiko-bot
2026-09-29 0:20 ` 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=179064120790.188287.14668641337564861331.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agoldberger@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=tariqt@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.