From: Clay Harris <bugs@claycon.org>
To: io-uring@vger.kernel.org
Subject: Feature request: Please implement IORING_OP_TEE
Date: Mon, 27 Apr 2020 10:40:32 -0500 [thread overview]
Message-ID: <20200427154031.n354uscqosf76p5z@ps29521.dreamhostps.com> (raw)
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.
next reply other threads:[~2020-04-27 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 15:40 Clay Harris [this message]
2020-04-27 15:55 ` Feature request: Please implement IORING_OP_TEE Jens Axboe
2020-04-27 18:03 ` Pavel Begunkov
2020-04-27 18:11 ` Jens Axboe
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 \
--in-reply-to=20200427154031.n354uscqosf76p5z@ps29521.dreamhostps.com \
--to=bugs@claycon.org \
--cc=io-uring@vger.kernel.org \
/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).