From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?SmFyaSBTZXBww6Rsw6QgPGphc2VAbm9jbG91ZC5vcmc+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: netdev@vger.kernel.org, kuba@kernel.org, sgoutham@marvell.com,
gakula@marvell.com, rkannoth@marvell.com, sbhatta@marvell.com,
bbhushan2@marvell.com, linux-yocto@lists.yoctoproject.org
Subject: Re: [PATCH net RESEND] octeontx2-pf: Fix RSS indirection table size
Date: Thu, 01 Oct 2026 00:30:15 +0000 [thread overview]
Message-ID: <179081461529.2189941.17932880589299208108.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928084711.2462571-1-jase@nocloud.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Sep 2026 11:47:11 +0300 you wrote:
> The conversion to the dedicated RSS context operations replaced the
> pointer to struct otx2_rss_ctx with an inline u32 ind_tbl[] array.
> However, otx2_rss_init() still uses sizeof(*rss->ind_tbl) to set rss_size.
> This now yields the size of one u32 (4), rather than the 256 entries in
> the indirection table.
>
> The RSS initialization and hardware programming loops use rss_size,
> so only four entries are initialized and programmed despite the NIX LF
> being allocated a 256-entry table. On an OCTEON CN102 with eight RX
> queues, the table contained 0, 1, 2, 3 followed by zeros. Traffic was
> concentrated on queue 0 and ethtool -X equal 8 did not correct the table.
>
> [...]
Here is the summary with links:
- [net,RESEND] octeontx2-pf: Fix RSS indirection table size
https://git.kernel.org/netdev/net/c/9e792901418d
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-10-01 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 9:14 [PATCH net] octeontx2-pf: Fix RSS indirection table size Jari Seppälä
2026-09-27 22:48 ` Jakub Kicinski
2026-09-28 8:47 ` [PATCH net RESEND] " Jari Seppälä
2026-09-29 2:36 ` Ratheesh Kannoth
2026-10-01 0:30 ` 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=179081461529.2189941.17932880589299208108.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?SmFyaSBTZXBww6Rsw6QgPGphc2VAbm9jbG91ZC5vcmc+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=bbhushan2@marvell.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-yocto@lists.yoctoproject.org \
--cc=netdev@vger.kernel.org \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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.