From: Joe Damato <joe@dama.to>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
donald.hunter@gmail.com, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, willemdebruijn.kernel@gmail.com,
ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next v4 0/4] net: ethtool: support including Flow Label in the flow hash for RSS
Date: Mon, 11 Aug 2025 17:40:24 -0700 [thread overview]
Message-ID: <aJqNeO36UpQ5KFI-@MacBook-Air.local> (raw)
In-Reply-To: <20250811234212.580748-1-kuba@kernel.org>
On Mon, Aug 11, 2025 at 04:42:08PM -0700, Jakub Kicinski wrote:
> Add support for using IPv6 Flow Label in Rx hash computation
> and therefore RSS queue selection.
I think this is really interesting work; thanks for doing this.
Do you think that the docs (Documentation/networking/scaling.rst) should be
updated to mention this setting and the side effects of using it?
If you agree, maybe that can be a future thing so as not to hold this change
back.
next prev parent reply other threads:[~2025-08-12 0:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 23:42 [PATCH net-next v4 0/4] net: ethtool: support including Flow Label in the flow hash for RSS Jakub Kicinski
2025-08-11 23:42 ` [PATCH net-next v4 1/4] " Jakub Kicinski
2025-08-12 0:27 ` Joe Damato
2025-08-14 9:39 ` Paolo Abeni
2025-08-11 23:42 ` [PATCH net-next v4 2/4] eth: fbnic: support RSS on IPv6 Flow Label Jakub Kicinski
2025-08-11 23:42 ` [PATCH net-next v4 3/4] eth: bnxt: " Jakub Kicinski
2025-08-12 6:44 ` Michael Chan
2025-08-11 23:42 ` [PATCH net-next v4 4/4] selftests: drv-net: add test for RSS on flow label Jakub Kicinski
2025-08-12 0:37 ` Joe Damato
2025-08-12 0:40 ` Joe Damato [this message]
2025-08-12 1:38 ` [PATCH net-next v4 0/4] net: ethtool: support including Flow Label in the flow hash for RSS Jakub Kicinski
2025-08-12 18:32 ` Joe Damato
2025-08-14 9:50 ` patchwork-bot+netdevbpf
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=aJqNeO36UpQ5KFI-@MacBook-Air.local \
--to=joe@dama.to \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=willemdebruijn.kernel@gmail.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.