From: Pavel Begunkov <asml.silence@gmail.com>
To: Askar Safin <safinaskar@mail.ru>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [POC RFC 0/3] splice(2) support for io_uring
Date: Mon, 6 Apr 2020 23:01:44 +0300 [thread overview]
Message-ID: <59c447cb-46b5-ac9d-3fdd-94d029e7f5dc@gmail.com> (raw)
In-Reply-To: <1586200181.435329676@f412.i.mail.ru>
[-- Attachment #1.1: Type: text/plain, Size: 682 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-06 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 19:09 [POC RFC 0/3] splice(2) support for io_uring Askar Safin
2020-04-06 20:01 ` Pavel Begunkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-22 0:05 Pavel Begunkov
2020-01-22 1:55 ` Jens Axboe
2020-01-22 3:11 ` Pavel Begunkov
2020-01-22 3:30 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59c447cb-46b5-ac9d-3fdd-94d029e7f5dc@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safinaskar@mail.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).