From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com
Subject: [PATCH net 0/4] bnxt_en: Fix RSS context and ntuple filter issues
Date: Wed, 28 Jan 2026 22:16:42 -0800 [thread overview]
Message-ID: <20260129061646.1417185-1-michael.chan@broadcom.com> (raw)
The first patch fixes the problem of ifup failing if one or more RSS
contexts were previously created. The 2nd patch is a cleanup patch
required by the 3rd patch which fixes ntuple filter deletion errors
in ifdown state. The 4th patch adds self tests to cover these failure
cases.
Pavan Chebbi (4):
bnxt_en: Fix RSS context delete logic
bnxt_en: Don't overload fw_vnic_id for RSS context's filters
bnxt_en: Fix deleting of Ntuple filters
selftests: drv-net: rss_ctx: test RSS contexts persist after ifdown/up
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 28 +++--
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 3 +-
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 12 +-
.../selftests/drivers/net/hw/rss_ctx.py | 117 +++++++++++++++++-
4 files changed, 141 insertions(+), 19 deletions(-)
--
2.51.0
next reply other threads:[~2026-01-29 6:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 6:16 Michael Chan [this message]
2026-01-29 6:16 ` [PATCH net 1/4] bnxt_en: Fix RSS context delete logic Michael Chan
2026-01-29 6:16 ` [PATCH net 2/4] bnxt_en: Don't overload fw_vnic_id for RSS context's filters Michael Chan
2026-01-29 6:16 ` [PATCH net 3/4] bnxt_en: Fix deleting of Ntuple filters Michael Chan
2026-01-29 6:16 ` [PATCH net 4/4] selftests: drv-net: rss_ctx: test RSS contexts persist after ifdown/up Michael Chan
2026-01-29 20:19 ` Joe Damato
2026-01-29 23:58 ` Jakub Kicinski
2026-01-30 2:03 ` Jakub Kicinski
2026-01-30 3:52 ` Pavan Chebbi
2026-01-30 5:24 ` Pavan Chebbi
2026-01-30 16:09 ` Jakub Kicinski
2026-02-04 16:15 ` Pavan Chebbi
2026-02-05 2:09 ` Jakub Kicinski
2026-02-05 5:41 ` Pavan Chebbi
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=20260129061646.1417185-1-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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