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-next>] [day] [month] [year] [list]
Date:   Wed, 24 Apr 2019 09:23:00 +0300
From:   Maxim Uvarov <>
Subject: RFC: zero copy recv()


On different conferences I see that people are trying to accelerate
network with putting packet processing with protocol level completely
to user space. It might be DPDK, ODP or AF_XDP  plus some network
stack on top of it. Then people are trying to test this solution with
some existence applications. And in better way do not modify
application binaries and just LD_PRELOAD sockets syscalls (recv(),
sendto() and etc). Current recv() expects that application allocates
memory and call will "copy" packet to that memory. Copy per packet is
slow.  Can we consider about implementing zero copy API calls
friendly? Can this change be accepted to kernel?

What are your thoughts?

Thank you,

Powered by blists - more mailing lists