[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c363e03-23e4-4ab2-b66a-aeb179cbacff@gmail.com>
Date: Thu, 11 Apr 2024 18:00:09 +0200
From: Richard Gobert <richardbgobert@...il.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, shuah@...nel.org,
dsahern@...nel.org, aduyck@...antis.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net-next v6 2/6] net: gro: add p_off param in
*_gro_complete
Willem de Bruijn wrote:
> And the latter parse the network header for total_len/payload_len, to
> find their original offset.
>
> It's also a bit of a hack. But a lot smaller patch, probably.
While producing a smaller change - this is a bit of a hacky code change.
My initial idea was to use network_offset added to the CB in the 4th commit
- making a very small change. (https://lore.kernel.org/netdev/446695cb-50b8-4187-bf11-63aedb6e9aed@gmail.com/)
Eric suggested it'd make more sense to pass it off as a parameter
throughout the complete chain.
Powered by blists - more mailing lists