From: Bhargava Marreddy <bhargava.marreddy@broadcom.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
vsrama-krishna.nemani@broadcom.com,
Bhargava Marreddy <bhargava.marreddy@broadcom.com>
Subject: [v6, net-next 00/10] Add more functionality to BNGE
Date: Fri, 5 Sep 2025 22:46:42 +0000 [thread overview]
Message-ID: <20250905224652.48692-1-bhargava.marreddy@broadcom.com> (raw)
Hi,
This patch series adds the infrastructure to make the netdevice
functional. It allocates data structures for core resources,
followed by their initialisation and registration with the firmware.
The core resources include the RX, TX, AGG, CMPL, and NQ rings,
as well as the VNIC. RX/TX functionality will be introduced in the
next patch series to keep this one at a reviewable size.
Changes from:
v5->v6
Addressed comments from Jakub Kicinski:
- Add appropriate error handling in several functions
- Enable device lock for bnge netdev ops
v4->v5
Addressed comments from Alok Tiwari
- Remove the redundant `size` assignment
v3->v4
Addressed a comment from Jakub Kicinski:
- To handle the page pool for both RX and AGG rings
- Use the appropriate page allocation mechanism for the AGG ring
when PAGE_SIZE is larger
v2->v3
Addressed a comment from Jakub Kicinski:
- Changed uses of atomic_t to refcount_t
v1->v2
Addressed warnings and errors in the patch series.
Thanks,
Bhargava Marreddy (10):
bng_en: make bnge_alloc_ring() self-unwind on failure
bng_en: Add initial support for RX and TX rings
bng_en: Add initial support for CP and NQ rings
bng_en: Introduce VNIC
bng_en: Initialise core resources
bng_en: Allocate packet buffers
bng_en: Allocate stat contexts
bng_en: Register rings with the firmware
bng_en: Register default VNIC
bng_en: Configure default VNIC
drivers/net/ethernet/broadcom/Kconfig | 1 +
drivers/net/ethernet/broadcom/bnge/bnge.h | 27 +
.../net/ethernet/broadcom/bnge/bnge_core.c | 16 +
drivers/net/ethernet/broadcom/bnge/bnge_db.h | 34 +
.../ethernet/broadcom/bnge/bnge_hwrm_lib.c | 485 ++++
.../ethernet/broadcom/bnge/bnge_hwrm_lib.h | 31 +
.../net/ethernet/broadcom/bnge/bnge_netdev.c | 2211 +++++++++++++++++
.../net/ethernet/broadcom/bnge/bnge_netdev.h | 251 +-
.../net/ethernet/broadcom/bnge/bnge_resc.c | 4 +-
.../net/ethernet/broadcom/bnge/bnge_resc.h | 1 +
.../net/ethernet/broadcom/bnge/bnge_rmem.c | 67 +-
.../net/ethernet/broadcom/bnge/bnge_rmem.h | 14 +
12 files changed, 3136 insertions(+), 6 deletions(-)
create mode 100644 drivers/net/ethernet/broadcom/bnge/bnge_db.h
--
2.47.3
next reply other threads:[~2025-09-05 17:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 22:46 Bhargava Marreddy [this message]
2025-09-05 22:18 ` Jakub Kicinski
2025-09-08 12:17 ` Bhargava Chenna Marreddy
2025-09-05 22:46 ` [v6, net-next 01/10] bng_en: make bnge_alloc_ring() self-unwind on failure Bhargava Marreddy
2025-09-05 22:46 ` [v6, net-next 02/10] bng_en: Add initial support for RX and TX rings Bhargava Marreddy
2025-09-09 2:39 ` Jakub Kicinski
2025-09-05 22:46 ` [v6, net-next 03/10] bng_en: Add initial support for CP and NQ rings Bhargava Marreddy
2025-09-05 22:46 ` [v6, net-next 04/10] bng_en: Introduce VNIC Bhargava Marreddy
2025-09-05 22:46 ` [v6, net-next 05/10] bng_en: Initialise core resources Bhargava Marreddy
2025-09-05 22:46 ` [v6, net-next 06/10] bng_en: Allocate packet buffers Bhargava Marreddy
2025-09-05 22:46 ` [v6, net-next 07/10] bng_en: Allocate stat contexts Bhargava Marreddy
2025-09-09 2:39 ` Jakub Kicinski
2025-09-05 22:46 ` [v6, net-next 08/10] bng_en: Register rings with the firmware Bhargava Marreddy
2025-09-05 22:46 ` [v6, net-next 09/10] bng_en: Register default VNIC Bhargava Marreddy
2025-09-05 22:46 ` [v6, net-next 10/10] bng_en: Configure " Bhargava Marreddy
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=20250905224652.48692-1-bhargava.marreddy@broadcom.com \
--to=bhargava.marreddy@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=vsrama-krishna.nemani@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
all inboxes | Powered by JetHome®