From: "Askar Safin" <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
[email protected]
Subject: Re: [POC RFC 0/3] splice(2) support for io_uring
Date: Mon, 06 Apr 2020 22:09:41 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
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?
==
Askar Safin
https://github.com/safinaskar
next reply other threads:[~2020-04-06 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 19:09 Askar Safin [this message]
2020-04-06 20:01 ` [POC RFC 0/3] splice(2) support for io_uring Pavel Begunkov
-- 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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