From: Chris J Arges <carges@cloudflare.com>
To: michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Stanislav Fomichev <sdf@fomichev.me>
Cc: kernel-team@cloudflare.com, Chris J Arges <carges@cloudflare.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH net-next 0/4] bnxt_en: add XDP RSS hash metadata support
Date: Fri, 27 Feb 2026 11:40:16 -0600 [thread overview]
Message-ID: <cover.1772211065.git.carges@cloudflare.com> (raw)
This series adds XDP RSS hash metadata extraction support for the bnxt_en
driver and includes selftests to validate the functionality. I was able
to test this on a BCM57414 NIC.
The driver changes introduce a bnxt_xdp_buff wrapper that carries
hardware RX completion descriptors alongside the xdp_buff, then use it
to implement bpf_xdp_metadata_rx_hash().
The selftest changes refactor common XDP/BPF helpers into a shared
library and add a new xdp_metadata test that verifies RSS hash
extraction for TCP and UDP traffic via device-bound XDP programs.
Chris J Arges (4):
bnxt_en: use bnxt_xdp_buff for xdp context
bnxt_en: Implement XDP RSS hash metadata extraction
selftests: net: move common xdp.py functions into lib
selftests: drv-net: xdp: Add rss_hash metadata tests
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 30 ++--
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 2 +
drivers/net/ethernet/broadcom/bnxt/bnxt_xdp.c | 47 +++++
drivers/net/ethernet/broadcom/bnxt/bnxt_xdp.h | 10 ++
tools/testing/selftests/drivers/net/Makefile | 1 +
.../selftests/drivers/net/lib/py/__init__.py | 2 +
tools/testing/selftests/drivers/net/xdp.py | 95 +++-------
.../selftests/drivers/net/xdp_metadata.py | 144 ++++++++++++++++
.../testing/selftests/net/lib/py/__init__.py | 2 +
tools/testing/selftests/net/lib/py/bpf.py | 68 ++++++++
.../selftests/net/lib/xdp_metadata.bpf.c | 163 ++++++++++++++++++
11 files changed, 482 insertions(+), 82 deletions(-)
create mode 100644 tools/testing/selftests/drivers/net/xdp_metadata.py
create mode 100644 tools/testing/selftests/net/lib/py/bpf.py
create mode 100644 tools/testing/selftests/net/lib/xdp_metadata.bpf.c
base-commit: 7dff99b354601dd01829e1511711846e04340a69
--
2.43.0
next reply other threads:[~2026-02-27 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 17:40 Chris J Arges [this message]
2026-02-27 17:40 ` [PATCH net-next 1/4] bnxt_en: use bnxt_xdp_buff for xdp context Chris J Arges
2026-02-27 17:40 ` [PATCH net-next 2/4] bnxt_en: Implement XDP RSS hash metadata extraction Chris J Arges
2026-02-27 19:04 ` Joe Damato
2026-02-27 17:40 ` [PATCH net-next 3/4] selftests: net: move common xdp.py functions into lib Chris J Arges
2026-02-27 19:10 ` Joe Damato
2026-02-27 17:40 ` [PATCH net-next 4/4] selftests: drv-net: xdp: Add rss_hash metadata tests Chris J Arges
2026-02-28 1:14 ` 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=cover.1772211065.git.carges@cloudflare.com \
--to=carges@cloudflare.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pavan.chebbi@broadcom.com \
--cc=sdf@fomichev.me \
/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.