[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJ6HROtg3m3z8Ac61e0Ex5HvgOTNavfG_W0j97B0XMZkw@mail.gmail.com>
Date: Wed, 4 Jun 2025 05:55:56 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Aurelien Aptel <aaptel@...dia.com>
Cc: linux-nvme@...ts.infradead.org, netdev@...r.kernel.org, sagi@...mberg.me,
hch@....de, kbusch@...nel.org, axboe@...com, chaitanyak@...dia.com,
davem@...emloft.net, kuba@...nel.org, Boris Pismenny <borisp@...dia.com>,
aurelien.aptel@...il.com, smalin@...dia.com, malin1024@...il.com,
ogerlitz@...dia.com, yorayz@...dia.com, galshalom@...dia.com,
mgurtovoy@...dia.com, tariqt@...dia.com, gus@...labora.com, pabeni@...hat.com,
dsahern@...nel.org, ast@...nel.org, jacob.e.keller@...el.com
Subject: Re: [PATCH v28 01/20] net: Introduce direct data placement tcp offload
On Wed, Jun 4, 2025 at 5:33 AM Aurelien Aptel <aaptel@...dia.com> wrote:
>
> Hi Eric,
>
> Any comments on this? Maybe I can clear up something?
Adding one bit in all skbs for such a narrow case is not very convincing to me.
I would prefer a disable/enable bit in the receiving socket, or a
global static key.
Powered by blists - more mailing lists