From: Jakub Kicinski <kuba@kernel.org>
To: Joe Damato <joe@dama.to>
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 18:38:05 -0700 [thread overview]
Message-ID: <20250811183805.087014a6@kernel.org> (raw)
In-Reply-To: <aJqNeO36UpQ5KFI-@MacBook-Air.local>
On Mon, 11 Aug 2025 17:40:24 -0700 Joe Damato wrote:
> Do you think that the docs (Documentation/networking/scaling.rst) should be
> updated to mention this setting and the side effects of using it?
I like writing docs but this feels a little too complicated to describe
in a paragraph in scaling.rst. The rest of the content in that file is
relatively noob-friendly. Dunno..
next prev parent reply other threads:[~2025-08-12 1:38 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 ` [PATCH net-next v4 0/4] net: ethtool: support including Flow Label in the flow hash for RSS Joe Damato
2025-08-12 1:38 ` Jakub Kicinski [this message]
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=20250811183805.087014a6@kernel.org \
--to=kuba@kernel.org \
--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=joe@dama.to \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).