From: Jakub Kicinski <kuba@kernel.org>
To: michael.chan@broadcom.com, pavan.chebbi@broadcom.com
Cc: willemdebruijn.kernel@gmail.com, netdev@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: [RFC net-next 0/6] net: ethtool: support including Flow Label in the flow hash for RSS
Date: Mon, 9 Jun 2025 10:34:36 -0700 [thread overview]
Message-ID: <20250609173442.1745856-1-kuba@kernel.org> (raw)
Add support for using IPv6 Flow Label in Rx hash computation
and therefore RSS queue selection.
Michael, Pavan, could you please give this series a whirl?
I see the capability bit in bnxt but none of the devices
I have access to seem to expose it. Note the test in the
last patch which you should be able to run. ethtool with
the support: https://github.com/kuba-moo/ethtool
Jakub Kicinski (6):
net: ethtool: factor out the validation for ETHTOOL_SRXFH
net: ethtool: support including Flow Label in the flow hash for RSS
eth: fbnic: support RSS on IPv6 Flow Label
eth: bnxt: support RSS on IPv6 Flow Label
selftests: drv-net: import things in lib one by one
selftests: drv-net: add test for RSS on flow label
.../testing/selftests/drivers/net/hw/Makefile | 1 +
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 1 +
include/uapi/linux/ethtool.h | 1 +
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 2 +
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 26 ++-
.../net/ethernet/meta/fbnic/fbnic_ethtool.c | 2 +-
drivers/net/ethernet/meta/fbnic/fbnic_rpc.c | 2 +
net/ethtool/ioctl.c | 56 ++++++-
.../drivers/net/hw/lib/py/__init__.py | 17 ++
.../drivers/net/hw/rss_flow_label.py | 151 ++++++++++++++++++
.../selftests/drivers/net/lib/py/__init__.py | 14 ++
11 files changed, 260 insertions(+), 13 deletions(-)
create mode 100755 tools/testing/selftests/drivers/net/hw/rss_flow_label.py
--
2.49.0
next reply other threads:[~2025-06-09 17:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 17:34 Jakub Kicinski [this message]
2025-06-09 17:34 ` [RFC net-next 1/6] net: ethtool: factor out the validation for ETHTOOL_SRXFH Jakub Kicinski
2025-06-09 17:34 ` [RFC net-next 2/6] net: ethtool: support including Flow Label in the flow hash for RSS Jakub Kicinski
2025-06-10 13:33 ` Willem de Bruijn
2025-06-09 17:34 ` [RFC net-next 3/6] eth: fbnic: support RSS on IPv6 Flow Label Jakub Kicinski
2025-06-09 17:34 ` [RFC net-next 4/6] eth: bnxt: " Jakub Kicinski
2025-06-09 18:24 ` Michael Chan
2025-06-09 18:44 ` Jakub Kicinski
2025-06-09 23:03 ` Michael Chan
2025-06-13 0:11 ` Michael Chan
2025-06-13 1:04 ` Jakub Kicinski
2025-06-23 4:20 ` Michael Chan
2025-06-09 17:34 ` [RFC net-next 5/6] selftests: drv-net: import things in lib one by one Jakub Kicinski
2025-06-09 17:34 ` [RFC net-next 6/6] selftests: drv-net: add test for RSS on flow label Jakub Kicinski
2025-06-09 18:26 ` [RFC net-next 0/6] net: ethtool: support including Flow Label in the flow hash for RSS Andrew Lunn
2025-06-09 18:58 ` Jakub Kicinski
2025-06-09 19:30 ` Andrew Lunn
2025-06-09 19:53 ` Jakub Kicinski
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=20250609173442.1745856-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@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 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).