From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>,
Alexander Viro <[email protected]>,
Stefan Metzmacher <[email protected]>,
[email protected], [email protected],
[email protected]
Subject: [PATCH v4 0/3] io_uring: add splice(2) support
Date: Mon, 24 Feb 2020 11:32:42 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
*on top of for-5.6 + async patches*
Not the fastets implementation, but I'd need to stir up/duplicate
splice.c bits to do it more efficiently.
note: rebase on top of the recent inflight patchset.
v2:
- u32 len and SQE layout changes (Jens)
- output file is in sqe->fd for automatic hash_reg_file support
- handle unbound_nonreg_file for the second fd
- file leaks fixed with REQ_F_NEED_CLEANUP
- place SPLICE_F_FD_IN_FIXED in splice flags (Jens)
- loff_t* -> loff_t, -1 means not specified offset
v3: [PATCH 3/3] changes
- fd u32 -> s32 (Stefan Metzmacher)
- add BUILD_BUG_SQE_ELEM() (Stefan Metzmacher)
- accept and ignore ioprio (Stefan Metzmacher)
- off_in -> splice_off_in
v4:
- rebase + a bit of function renaming
- make file_get/put accept req instead of ctx (Jens)
- fix lost REQ_F_FIXED_FILE
Pavel Begunkov (3):
splice: make do_splice public
io_uring: add interface for getting files
io_uring: add splice(2) support
fs/io_uring.c | 181 ++++++++++++++++++++++++++++------
fs/splice.c | 6 +-
include/linux/splice.h | 3 +
include/uapi/linux/io_uring.h | 14 ++-
4 files changed, 171 insertions(+), 33 deletions(-)
--
2.24.0
next reply other threads:[~2020-02-24 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 8:32 Pavel Begunkov [this message]
2020-02-24 8:32 ` [PATCH v4 1/3] splice: make do_splice public Pavel Begunkov
2020-02-24 8:32 ` [PATCH v4 2/3] io_uring: add interface for getting files Pavel Begunkov
2020-02-24 8:32 ` [PATCH v4 3/3] io_uring: add splice(2) support Pavel Begunkov
2020-02-24 15:35 ` [PATCH v4 0/3] " Jens Axboe
2020-02-24 22:34 ` Jens Axboe
2020-02-24 22:51 ` Pavel Begunkov
2020-02-24 22:53 ` Pavel Begunkov
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] \
[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