[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF=yD-JWDzc54_2bF2KkvKxDL3jD+COWUDx9_P5DVF7q8T=bJA@mail.gmail.com>
Date: Thu, 18 Jul 2024 23:24:41 -0400
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Bailey Forrest <bcf@...gle.com>
Cc: Praveen Kaligineedi <pkaligineedi@...gle.com>, netdev@...r.kernel.org, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, willemb@...gle.com,
shailend@...gle.com, hramamurthy@...gle.com, csully@...gle.com,
jfraker@...gle.com, stable@...r.kernel.org,
Jeroen de Borst <jeroendb@...gle.com>
Subject: Re: [PATCH net] gve: Fix an edge case for TSO skb validity check
On Thu, Jul 18, 2024 at 8:28 PM Bailey Forrest <bcf@...gle.com> wrote:
>
> On Thu, Jul 18, 2024 at 4:07 PM Willem de Bruijn
> <willemdebruijn.kernel@...il.com> wrote:
> >
> > This however loops skb->len / gso_size. While the above modulo
> > operation skips many segments that span a frag. Not sure if the more
> > intuitive approach could be as performant.
>
> Yes, the original intention of the code was to loop over nr_frags,
> instead of (skb->len / gso_size).
>
> But perhaps that's premature optimization if it makes the code
> significantly harder to follow.
Thanks. I don't mean to ask for a wholesale rewrite if not needed.
But perhaps the logic can be explained in the commit in a way
that it is more immediately obvious.
Praveen suggested that. I'll respond to his reply in more detail.
Powered by blists - more mailing lists