From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <leonro@nvidia.com>,
<jgg@nvidia.com>, <bhargava.marreddy@broadcom.com>,
<rahul-rg.gupta@broadcom.com>,
<vsrama-krishna.nemani@broadcom.com>,
<rajashekar.hudumula@broadcom.com>, <ajit.khaparde@broadcom.com>,
Siva Reddy Kallam <siva.kallam@broadcom.com>,
Dharmender Garg <dharmender.garg@broadcom.com>,
"Yendapally Reddy Dhananjaya Reddy"
<yendapally.reddy@broadcom.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>, <horms@kernel.org>
Subject: Re: [PATCH net v2] bnge/bng_re: fix ring ID widths
Date: Fri, 10 Jul 2026 12:06:00 +0200 [thread overview]
Message-ID: <c108a5ec-8740-431e-849d-581c136f404d@intel.com> (raw)
In-Reply-To: <20260704164747.1995227-1-vikas.gupta@broadcom.com>
On 7/4/26 18:47, Vikas Gupta wrote:
> Firmware requires more than 16 bits to address TX ring IDs for its
> internal QP management. Widen the associated HSI ring ID fields to
> 32 bits. The values firmware assigns remain within 24 bits, bounded
> by the hardware doorbell XID field.
>
> RX, completion, and NQ ring IDs are unaffected and remain 16-bit.
Here you mention Rx is unaffected. But you touch multiple places that
are Rx specific (some comments below).
[..]
> --- a/drivers/net/ethernet/broadcom/bnge/bnge.h
> +++ b/drivers/net/ethernet/broadcom/bnge/bnge.h
> @@ -36,6 +36,7 @@ struct bnge_pf_info {
> };
>
> #define INVALID_HW_RING_ID ((u16)-1)
> +#define INVALID_HW_RING_ID_32BIT (U32_MAX)
OK, there is much more usage of INVALID_HW_RING_ID than places touched
by this patch.
[...]
> +++ b/drivers/net/ethernet/broadcom/bnge/bnge_netdev.c
> @@ -1327,12 +1327,12 @@ static int bnge_alloc_core(struct bnge_net *bn)
> return rc;
> }
>
> -u16 bnge_cp_ring_for_rx(struct bnge_rx_ring_info *rxr)
> +u32 bnge_cp_ring_for_rx(struct bnge_rx_ring_info *rxr)
and here you change Rx ring ID width.
> {
> return rxr->rx_cpr->ring_struct.fw_ring_id;
> }
>
> -u16 bnge_cp_ring_for_tx(struct bnge_tx_ring_info *txr)
> +u32 bnge_cp_ring_for_tx(struct bnge_tx_ring_info *txr)
> {
> return txr->tx_cpr->ring_struct.fw_ring_id;
> }
> @@ -1375,12 +1375,12 @@ static void bnge_init_nq_tree(struct bnge_net *bn)
> struct bnge_nq_ring_info *nqr = &bn->bnapi[i]->nq_ring;
> struct bnge_ring_struct *ring = &nqr->ring_struct;
>
> - ring->fw_ring_id = INVALID_HW_RING_ID;
> + ring->fw_ring_id = INVALID_HW_RING_ID_32BIT;
> for (j = 0; j < nqr->cp_ring_count; j++) {
> struct bnge_cp_ring_info *cpr = &nqr->cp_ring_arr[j];
>
> ring = &cpr->ring_struct;
> - ring->fw_ring_id = INVALID_HW_RING_ID;
> + ring->fw_ring_id = INVALID_HW_RING_ID_32BIT;
> }
> }
> }
> @@ -1637,7 +1637,7 @@ static void bnge_init_one_rx_ring_rxbd(struct bnge_net *bn,
ditto Rx
>
> ring = &rxr->rx_ring_struct;
> bnge_init_rxbd_pages(ring, type);
> - ring->fw_ring_id = INVALID_HW_RING_ID;
> + ring->fw_ring_id = INVALID_HW_RING_ID_32BIT;
> }
>
> static void bnge_init_one_agg_ring_rxbd(struct bnge_net *bn,
> @@ -1647,7 +1647,7 @@ static void bnge_init_one_agg_ring_rxbd(struct bnge_net *bn,
ditto Rx, and in some other places too
next prev parent reply other threads:[~2026-07-10 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 16:47 [PATCH net v2] bnge/bng_re: fix ring ID widths Vikas Gupta
2026-07-04 18:34 ` Andrew Lunn
2026-07-10 6:10 ` Vikas Gupta
2026-07-10 16:42 ` Andrew Lunn
2026-07-10 10:06 ` Przemek Kitszel [this message]
2026-07-10 14:25 ` Vikas Gupta
2026-07-11 4:16 ` Przemek Kitszel
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=c108a5ec-8740-431e-849d-581c136f404d@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=dharmender.garg@broadcom.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rahul-rg.gupta@broadcom.com \
--cc=rajashekar.hudumula@broadcom.com \
--cc=siva.kallam@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vsrama-krishna.nemani@broadcom.com \
--cc=yendapally.reddy@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