From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, saeedm@nvidia.com,
tariqt@nvidia.com, mbloch@nvidia.com, leon@kernel.org,
horms@kernel.org, shuah@kernel.org, netdev@vger.kernel.org,
maxime.chevallier@bootlin.com, gal@nvidia.com,
willemb@google.com, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/4] ethtool: Dynamic RSS context indirection table resizing
Date: Tue, 24 Mar 2026 01:50:10 +0000 [thread overview]
Message-ID: <177431701054.413704.17760247587470177196.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260320085826.1957255-1-bjorn@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 20 Mar 2026 09:58:20 +0100 you wrote:
> Hi!
>
> Some NICs (e.g. bnxt) change their RSS indirection table size based on
> the queue count, because the hardware table is a shared resource. The
> ethtool core locks ctx->indir_size at context creation, so drivers
> have to reject channel changes when RSS contexts exist.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/4] ethtool: Track user-provided RSS indirection table size
https://git.kernel.org/netdev/net-next/c/0475f9e779b4
- [net-next,v7,2/4] ethtool: Add RSS indirection table resize helpers
https://git.kernel.org/netdev/net-next/c/02bcb20083b2
- [net-next,v7,3/4] bnxt_en: Resize RSS contexts on channel count change
https://git.kernel.org/netdev/net-next/c/57cdfe0dc70b
- [net-next,v7,4/4] selftests: rss_drv: Add RSS indirection table resize tests
https://git.kernel.org/netdev/net-next/c/10329ce49285
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-03-24 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 8:58 [PATCH net-next v7 0/4] ethtool: Dynamic RSS context indirection table resizing Björn Töpel
2026-03-20 8:58 ` [PATCH net-next v7 1/4] ethtool: Track user-provided RSS indirection table size Björn Töpel
2026-03-20 8:58 ` [PATCH net-next v7 2/4] ethtool: Add RSS indirection table resize helpers Björn Töpel
2026-03-20 8:58 ` [PATCH net-next v7 3/4] bnxt_en: Resize RSS contexts on channel count change Björn Töpel
2026-03-20 8:58 ` [PATCH net-next v7 4/4] selftests: rss_drv: Add RSS indirection table resize tests Björn Töpel
2026-03-24 1:50 ` 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=177431701054.413704.17760247587470177196.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mbloch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=saeedm@nvidia.com \
--cc=shuah@kernel.org \
--cc=tariqt@nvidia.com \
--cc=willemb@google.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