From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, Clay Harris <[email protected]>
Cc: [email protected]
Subject: Re: Feature request: Please implement IORING_OP_TEE
Date: Mon, 27 Apr 2020 12:11:28 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 4/27/20 12:03 PM, Pavel Begunkov wrote:
> On 27/04/2020 18:55, Jens Axboe wrote:
>> On 4/27/20 9:40 AM, Clay Harris wrote:
>>> I was excited to see IORING_OP_SPLICE go in, but disappointed that tee
>>> didn't go in at the same time. It would be very useful to copy pipe
>>> buffers in an async program.
>>
>> Pavel, care to wire up tee? From a quick look, looks like just exposing
>> do_tee() and calling that, so should be trivial.
>
> Yes, should be, I'll add it
Only other thing I spotted is making the inode lock / double lock honor
nowait, which is separate from the SPLICE_F_NONBLOCK flag.
--
Jens Axboe
next prev parent reply other threads:[~2020-04-27 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 15:40 Feature request: Please implement IORING_OP_TEE Clay Harris
2020-04-27 15:55 ` Jens Axboe
2020-04-27 18:03 ` Pavel Begunkov
2020-04-27 18:11 ` Jens Axboe [this message]
2020-04-27 18:22 ` Jann Horn
2020-04-27 20:02 ` Jens Axboe
2020-04-29 15:57 ` Pavel Begunkov
2020-04-27 20:17 ` Clay Harris
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] \
/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