From: Stephen Hemminger <stephen@networkplumber.org>
To: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
Cc: dev@dpdk.org, kishore.padmanabha@broadcom.com,
Keegan Freyhof <keegan.freyhof@broadcom.com>
Subject: Re: [PATCH v2] net/bnxt: add support for queue size of 16384
Date: Mon, 21 Sep 2026 08:52:50 -0700 [thread overview]
Message-ID: <20260921085250.46018e60@phoenix.local> (raw)
In-Reply-To: <20260921025903.1034720-1-Mohammad-Shuab.Siddique@broadcom.com>
On Sun, 20 Sep 2026 20:59:03 -0600
Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com> wrote:
> From: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
>
> The driver only supported queue sizes up to 4096 for Tx and 8192 for
> Rx. Raise both to 16384. The completion ring for a Rx ring is sized
> at 2x the Rx ring size, further multiplied by 4 when the aggregation
> ring is in use (8x total), so at 16384 it can reach 131072, above
> uint16_t range - widen the ring index/counter variables touched by
> that path to uint32_t.
>
> Signed-off-by: Keegan Freyhof <keegan.freyhof@broadcom.com>
> Signed-off-by: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
> ---
[PATCH v2] net/bnxt: add support for queue size of 16384
Warning: the change of BNXT_MAX_MTU and BNXT_NUM_VLANS to UL is
unrelated to queue size and is not described. It changes the type of
BNXT_MAX_PKT_LEN to unsigned long. Drop it, or split it out with a
reason.
Warning: MAX_CP_DESC_CNT is bumped to 32K and gains a comment saying
it is unused and the real worst case is 131072. If it is unused,
delete it.
next prev parent reply other threads:[~2026-09-21 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 3:28 [PATCH] net/bnxt: add support for queue size of 16384 Mohammad Shuab Siddique
2026-09-21 2:59 ` [PATCH v2] " Mohammad Shuab Siddique
2026-09-21 15:52 ` Stephen Hemminger [this message]
2026-09-23 22:46 ` Mohammad Shuab Siddique
2026-09-29 0:22 ` [PATCH v3] " Mohammad Shuab Siddique
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=20260921085250.46018e60@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=keegan.freyhof@broadcom.com \
--cc=kishore.padmanabha@broadcom.com \
--cc=mohammad-shuab.siddique@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 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.