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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <59c447cb-46b5-ac9d-3fdd-94d029e7f5dc@gmail.com>
Date:   Mon, 6 Apr 2020 23:01:44 +0300
From:   Pavel Begunkov <asml.silence@...il.com>
To:     Askar Safin <safinaskar@...l.ru>
Cc:     io-uring@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>
Subject: Re: [POC RFC 0/3] splice(2) support for io_uring

On 06/04/2020 22:09, Askar Safin wrote:
> Hi. Thanks for your splice io_uring patch. Maybe it will be good idea to add uring operation, which will unify splice, sendfile and copy_file_range instead of just IORING_OP_SPLICE?

It doesn't have to follow splice(2) semantics, so can be extended, in theory.

Though I don't see much profit in doing that for now. sendfile(2) is done by
splicing through an internal pipe, and this pipe will complicate things for
io-wq (i.e. io_uring's thread pool). On the other hand, it'd be of the same
performance and even more flexible to send 2 linked splice requests with a
pre-allocated pipe from the userspace.

-- 
Pavel Begunkov



Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ