From: Joe Damato <joe@dama.to>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: netdev@vger.kernel.org, Michael Chan <michael.chan@broadcom.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
horms@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] bnxt_en: Prevent queue stop with deferred completions
Date: Sat, 29 Aug 2026 08:15:24 -0700 [thread overview]
Message-ID: <apL3jDnQuMfifkj6@devvm20253.cco0.facebook.com> (raw)
In-Reply-To: <CALs4sv1v7E_pxmdcNzxf8GyR7=-B26J5Z1YZ7fc4Y2Oc7Le8yg@mail.gmail.com>
On Sat, Aug 29, 2026 at 02:57:59PM +0530, Pavan Chebbi wrote:
> > if (unlikely(bnxt_tx_avail(bp, txr) < bds_needed)) {
> > netif_txq_try_stop(txq, bnxt_tx_avail(bp, txr),
> > bp->tx_wake_thresh);
> > - return NETDEV_TX_BUSY;
> > + goto tx_busy;
> > }
> >
> > /* BD backpressure alone cannot prevent overwriting in-flight
> > @@ -77,7 +77,7 @@ netdev_tx_t bnxt_sw_udp_gso_xmit(struct bnxt *bp,
> > */
> > if (!netif_txq_maybe_stop(txq, bnxt_inline_avail(txr),
> > num_segs, num_segs))
> > - return NETDEV_TX_BUSY;
> > + goto tx_busy;
> >
> > if (unlikely(tso_dma_map_init(&map, &pdev->dev, skb, hdr_len)))
> > goto drop;
> > @@ -235,4 +235,17 @@ netdev_tx_t bnxt_sw_udp_gso_xmit(struct bnxt *bp,
> > dev_kfree_skb_any(skb);
> > dev_core_stats_tx_dropped_inc(bp->dev);
> > return NETDEV_TX_OK;
> > +
> > +tx_busy:
> > + if (txr->kick_pending) {
> > + u16 kick_prod = txr->kick_prod;
> > + struct tx_bd *txbd0;
> > +
> > + txbd0 = &txr->tx_desc_ring[TX_RING(bp, kick_prod)]
> > + [TX_IDX(kick_prod)];
> > + txbd0->tx_bd_len_flags_type &=
> > + cpu_to_le32(~TX_BD_FLAGS_NO_CMPL);
>
> Should we not do a bnxt_txr_db_kick() also? It maybe a good idea to do
> it in success case also instead of bnxt_db_write..
When this function returns, the caller writes the doorbell, so we should be
good.
prev parent reply other threads:[~2026-08-29 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 23:02 Joe Damato
2026-08-28 3:21 ` Xuanqiang Luo
2026-08-28 14:57 ` Eric Dumazet
2026-08-29 9:27 ` Pavan Chebbi
2026-08-29 15:15 ` Joe Damato [this message]
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=apL3jDnQuMfifkj6@devvm20253.cco0.facebook.com \
--to=joe@dama.to \
--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=stable@vger.kernel.org \
/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®