DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
Cc: dev@dpdk.org, kishore.padmanabha@broadcom.com
Subject: Re: [PATCH v2] net/bnxt: add Tx DMA error stat counter
Date: Mon, 21 Sep 2026 08:51:25 -0700	[thread overview]
Message-ID: <20260921085125.7cc04e04@phoenix.local> (raw)
In-Reply-To: <20260921022703.1034465-1-Mohammad-Shuab.Siddique@broadcom.com>

On Sun, 20 Sep 2026 20:27:03 -0600
Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com> wrote:

> From: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
> 
> Hardware already reports an invalid/bad DMA address on a Tx BD via
> the TX_CMPL_ERRORS_DMA_ERROR bit in the Tx completion record, but the
> driver never inspected it, so a bad mbuf->buf_iova on Tx completed
> silently with no visibility.
> 
> Check the bit in bnxt_handle_tx_cp() and in the AVX2/SSE vector
> Tx-completion handlers, and count occurrences in a new per-queue
> tx_dma_err counter. The counter is folded into the standard oerrors
> stat and also exposed as a named xstat (tx_dma_err_pkts) for
> finer-grained visibility.
> 
> Signed-off-by: Mohammad Shuab Siddique <mohammad-shuab.siddique@broadcom.com>
> ---

[PATCH v2] net/bnxt: add Tx DMA error stat counter

Warning: tx_dma_err is a per-queue, single-writer counter but uses
rte_atomic_fetch_add_explicit() in the completion fast path. That is
a locked RMW for no benefit. Use a plain increment. The existing
tx_mbuf_drop pattern is not a reason to extend it.

Warning: bnxt_handle_tx_cp_vec() in bnxt_rxtx_vec_neon.c is not
updated. arm64 never counts DMA errors.

Warning: the release note says "per-queue xstat", but the patch
exposes a single port-wide sum. Fix one or the other.

Info: "tx_dma_err_pkts" counts completions, not packets. Vector
completions cover opaque packets, and with the following coalescing
patch one completion covers many. Rename the xstat or count packets.

  reply	other threads:[~2026-09-21 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  3:28 [PATCH] net/bnxt: add Tx DMA error stat counter Mohammad Shuab Siddique
2026-09-21  2:27 ` [PATCH v2] " Mohammad Shuab Siddique
2026-09-21 15:51   ` Stephen Hemminger [this message]
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=20260921085125.7cc04e04@phoenix.local \
    --to=stephen@networkplumber.org \
    --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