netdev - Re: MSG_ZEROCOPY

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:   Tue, 10 Nov 2020 16:09:02 -0800
From:   Jonathan Lemon <jonathan.lemon@...il.com>
To:     Victor Stewart <v@...etag.social>
Cc:     netdev@...r.kernel.org
Subject: Re: MSG_ZEROCOPY_FIXED

On Sun, Nov 08, 2020 at 05:04:41PM +0000, Victor Stewart wrote:
> hi all,
> 
> i'm seeking input / comment on the idea of implementing full fledged
> zerocopy UDP networking that uses persistent buffers allocated in
> userspace... before I go off on a solo tangent with my first patches
> lol.
> 
> i'm sure there's been lots of thought/discussion on this before. of
> course Willem added MSG_ZEROCOPY on the send path (pin buffers on
> demand / per send). and something similar to what I speak of exists
> with TCP_ZEROCOPY_RECEIVE.
> 
> i envision something like a new flag like MSG_ZEROCOPY_FIXED that
> "does the right thing" in the send vs recv paths.

See the netgpu patches that I posted earlier; these will handle
protocol independent zerocopy sends/receives.  I do have a working
UDP receive implementation which will be posted with an updated
patchset.
--
Jonathan