From: Stephen Hemminger <stephen@networkplumber.org>
To: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
Cc: dev@dpdk.org, kishore.padmanabha@broadcom.com,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH] net/bnxt: enable Tx completion coalescing in hardware
Date: Mon, 21 Sep 2026 08:52:05 -0700 [thread overview]
Message-ID: <20260921085205.5e52f0f9@phoenix.local> (raw)
In-Reply-To: <20260921025755.1034702-1-Mohammad-Shuab.Siddique@broadcom.com>
On Sun, 20 Sep 2026 20:57:55 -0600
Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com> wrote:
> From: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
>
> P7 devices support Tx completion coalescing in hardware: the driver
> can program the Tx coalescing parameters during Tx ring allocation
> instead of always disabling it. Use the wthresh config option
> provided in ethdev to select the coalescing value for the Tx rings.
>
> A value of 0 disables the feature. A value of 254 for wthresh is the
> max allowable setting; the driver converts the provided value to the
> nearest power of 2 for the hardware setting (1 rounds up to 2, which
> maps to the same COAL_4 setting as an exact 4; 254 rounds up to 256).
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Signed-off-by: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
> ---
[PATCH] net/bnxt: enable Tx completion coalescing in hardware
Error: does not apply to main without fuzz (see summary).
Warning: this adds user-visible behaviour keyed off
tx_thresh.wthresh. It needs a doc/guides/nics/bnxt.rst entry and a
release note.
next prev parent reply other threads:[~2026-09-21 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 2:57 [PATCH] net/bnxt: enable Tx completion coalescing in hardware Mohammad Shuab Siddique
2026-09-21 15:52 ` Stephen Hemminger [this message]
2026-09-29 0:23 ` [PATCH v2] " 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=20260921085205.5e52f0f9@phoenix.local \
--to=stephen@networkplumber.org \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox