netdev - Re: [PATCH v25 00/20] nvme-tcp receive offloads

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 31 May 2024 08:11:42 +0200
From: Christoph Hellwig <hch@....de>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Aurelien Aptel <aaptel@...dia.com>, 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
Subject: Re: [PATCH v25 00/20] nvme-tcp receive offloads

FYI, I still absolutely detest this code.  I know people want to
avoid the page copy for NVMe over TCP (or any TCP based storage
protocols for that matter), but having these weird vendors specific
hooks all the way up into the application protocol are just horrible.

IETF has standardized a generic data placement protocol, which is
part of iWarp.  Even if folks don't like RDMA it exists to solve
exactly these kinds of problems of data placement.   And if we can't
arse folks into standard data placement methods we at least need it
vendor independent and without hooks into the actual protocol
driver.