public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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, leon@kernel.org
Subject: Re: [net-next v3 08/12] net: bnxt: Implement software USO
Date: Thu, 19 Mar 2026 10:12:10 -0700	[thread overview]
Message-ID: <abwuamlgUcIV43A6@devvm20253.cco0.facebook.com> (raw)
In-Reply-To: <CALs4sv3i9qk879+OFyj1Ecq6-Kkuuu=GAY2hJCFYOfFg3sy_Jg@mail.gmail.com>

On Thu, Mar 19, 2026 at 05:11:03PM +0530, Pavan Chebbi wrote:
> <...>
> 
> > +
> > +       hdr_len = tso_start(skb, &tso);
> > +       mss = skb_shinfo(skb)->gso_size;
> > +       total_payload = skb->len - hdr_len;
> > +       num_segs = DIV_ROUND_UP(total_payload, mss);
> > +
> > +       /* Zero the csum fields so tso_build_hdr will propagate zeroes into
> > +        * every segment header. HW csum offload will recompute from scratch.
> > +        */
> > +       udp_hdr(skb)->check = 0;
> > +       if (!tso.ipv6)
> > +               ip_hdr(skb)->check = 0;
> > +
> > +       if (unlikely(num_segs <= 1))
> > +               return NETDEV_TX_OK;
> 
> goto drop would be more appropriate?

Yes, you are right. Good catch. Will fix it in the v4; thanks for reviewing!

  reply	other threads:[~2026-03-19 17:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 19:13 [net-next v3 00/12] Add TSO map-once DMA helpers and bnxt SW USO support Joe Damato
2026-03-18 19:13 ` [net-next v3 01/12] net: tso: Introduce tso_dma_map Joe Damato
2026-03-18 19:13 ` [net-next v3 02/12] net: tso: Add tso_dma_map helpers Joe Damato
2026-03-19  7:39   ` Leon Romanovsky
2026-03-19 17:09     ` Joe Damato
2026-03-19 19:34       ` Leon Romanovsky
2026-03-18 19:13 ` [net-next v3 03/12] net: bnxt: Export bnxt_xmit_get_cfa_action Joe Damato
2026-03-19 11:32   ` Pavan Chebbi
2026-03-18 19:13 ` [net-next v3 04/12] net: bnxt: Add a helper for tx_bd_ext Joe Damato
2026-03-19 11:33   ` Pavan Chebbi
2026-03-18 19:13 ` [net-next v3 05/12] net: bnxt: Use dma_unmap_len for TX completion unmapping Joe Damato
2026-03-19 11:35   ` Pavan Chebbi
2026-03-18 19:13 ` [net-next v3 06/12] net: bnxt: Add TX inline buffer infrastructure Joe Damato
2026-03-18 19:13 ` [net-next v3 07/12] net: bnxt: Add boilerplate GSO code Joe Damato
2026-03-18 19:13 ` [net-next v3 08/12] net: bnxt: Implement software USO Joe Damato
2026-03-19 11:41   ` Pavan Chebbi
2026-03-19 17:12     ` Joe Damato [this message]
2026-03-18 19:13 ` [net-next v3 09/12] net: bnxt: Add SW GSO completion and teardown support Joe Damato
2026-03-18 19:13 ` [net-next v3 10/12] net: bnxt: Dispatch to SW USO Joe Damato
2026-03-18 19:13 ` [net-next v3 11/12] net: netdevsim: Add support for " Joe Damato
2026-03-18 19:13 ` [net-next v3 12/12] selftests: drv-net: Add USO test Joe Damato

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=abwuamlgUcIV43A6@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