[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <253y1h0j7j6.fsf@mtr-vdi-124.i-did-not-set--mail-host-address--so-tickle-me>
Date: Thu, 21 Sep 2023 10:43:25 +0300
From: Aurelien Aptel <aaptel@...dia.com>
To: David Ahern <dsahern@...nel.org>, 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
Cc: 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,
edumazet@...gle.com, pabeni@...hat.com, imagedong@...cent.com
Subject: Re: [PATCH v15 01/20] net: Introduce direct data placement tcp offload
David Ahern <dsahern@...nel.org> writes:
> Not consolidating frags into linear is a requirement for any Rx ZC
> solution (e.g., the gpu devmem RFC set and accompanying io_uring set for
> userspace memory). Meaning, the bit can be more generic and less tied to
> ulp_ddp.
In our view the ULP Direct Data Placement has a very specific design and
avoiding skb coalescing is just one aspect of it.
It would be hard to make it generic for any type of zero copy design. We
can rename the bit to "ddp" or "zerocopy" if you prefer but it might end
up being more misleading.
Powered by blists - more mailing lists