netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: 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,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v4 0/4] net: ethtool: support including Flow Label in the flow hash for RSS
Date: Mon, 11 Aug 2025 16:42:08 -0700	[thread overview]
Message-ID: <20250811234212.580748-1-kuba@kernel.org> (raw)

Add support for using IPv6 Flow Label in Rx hash computation
and therefore RSS queue selection.

v4:
 - adjust the 2 tuple / 4 tuple condition in bnxt
v3: https://lore.kernel.org/20250724015101.186608-1-kuba@kernel.org
 - change the bnxt driver, bits are now exclusive
 - check for RPS/RFS in the test
v2:  https://lore.kernel.org/20250722014915.3365370-1-kuba@kernel.org
RFC: https://lore.kernel.org/20250609173442.1745856-1-kuba@kernel.org

Jakub Kicinski (4):
  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: add test for RSS on flow label

 Documentation/netlink/specs/ethtool.yaml      |   3 +
 .../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 |  20 ++-
 .../net/ethernet/meta/fbnic/fbnic_ethtool.c   |   2 +-
 drivers/net/ethernet/meta/fbnic/fbnic_rpc.c   |   2 +
 net/ethtool/ioctl.c                           |  25 +++
 net/ethtool/rss.c                             |  27 +--
 .../drivers/net/hw/rss_flow_label.py          | 167 ++++++++++++++++++
 11 files changed, 233 insertions(+), 18 deletions(-)
 create mode 100755 tools/testing/selftests/drivers/net/hw/rss_flow_label.py

-- 
2.50.1


             reply	other threads:[~2025-08-11 23:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 23:42 Jakub Kicinski [this message]
2025-08-11 23:42 ` [PATCH net-next v4 1/4] net: ethtool: support including Flow Label in the flow hash for RSS 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
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=20250811234212.580748-1-kuba@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=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).