public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Damato <joe@dama.to>
To: netdev@vger.kernel.org, Michael Chan <michael.chan@broadcom.com>,
	Pavan Chebbi <pavan.chebbi@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>
Cc: horms@kernel.org, linux-kernel@vger.kernel.org, leon@kernel.org
Subject: Re: [net-next v9 07/10] net: bnxt: Implement software USO
Date: Tue, 7 Apr 2026 16:23:00 -0700	[thread overview]
Message-ID: <adWR1OiPlQCJ8idj@devvm20253.cco0.facebook.com> (raw)
In-Reply-To: <20260407220313.3990909-8-joe@dama.to>

On Tue, Apr 07, 2026 at 03:03:03PM -0700, Joe Damato wrote:

[...]

>  v9:
>    - Added inline slot check to prevent possible overwriting of in-flight
>      headers (suggested by AI).

[...]

>  netdev_tx_t bnxt_sw_udp_gso_xmit(struct bnxt *bp,
>  				 struct bnxt_tx_ring_info *txr,
>  				 struct netdev_queue *txq,
>  				 struct sk_buff *skb)
>  {

[...]

> +
> +	/* BD backpressure alone cannot prevent overwriting in-flight
> +	 * headers in the inline buffer. Check slot availability directly.
> +	 */
> +	slots = txr->tx_inline_prod - txr->tx_inline_cons;
> +	slots = BNXT_SW_USO_MAX_SEGS - slots;
> +
> +	if (unlikely(slots < num_segs)) {
> +		netif_txq_try_stop(txq, slots, num_segs);
> +		return NETDEV_TX_BUSY;

This is the check I added. AI says this is wrong and netdev_queues.h says:

  * @get_desc must be a formula or a function call, it must always
  * return up-to-date information when evaluated!

which I obviously failed to do, so I'm pretty sure I got this wrong.

  reply	other threads:[~2026-04-07 23:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 22:02 [net-next v9 00/10] Add TSO map-once DMA helpers and bnxt SW USO support Joe Damato
2026-04-07 22:02 ` [net-next v9 01/10] net: tso: Introduce tso_dma_map and helpers Joe Damato
2026-04-07 22:02 ` [net-next v9 02/10] net: bnxt: Export bnxt_xmit_get_cfa_action Joe Damato
2026-04-07 22:02 ` [net-next v9 03/10] net: bnxt: Add a helper for tx_bd_ext Joe Damato
2026-04-07 22:03 ` [net-next v9 04/10] net: bnxt: Use dma_unmap_len for TX completion unmapping Joe Damato
2026-04-07 22:03 ` [net-next v9 05/10] net: bnxt: Add TX inline buffer infrastructure Joe Damato
2026-04-07 22:03 ` [net-next v9 06/10] net: bnxt: Add boilerplate GSO code Joe Damato
2026-04-07 22:03 ` [net-next v9 07/10] net: bnxt: Implement software USO Joe Damato
2026-04-07 23:23   ` Joe Damato [this message]
2026-04-07 22:03 ` [net-next v9 08/10] net: bnxt: Add SW GSO completion and teardown support Joe Damato
2026-04-07 22:03 ` [net-next v9 09/10] net: bnxt: Dispatch to SW USO Joe Damato
2026-04-07 22:03 ` [net-next v9 10/10] selftests: drv-net: Add USO test Joe Damato
2026-04-08  3:14   ` Jakub Kicinski

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=adWR1OiPlQCJ8idj@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=leon@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 \
    /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