From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Jens Axboe <axboe@fb.com>,
Nicholas Bellinger <nab@linux-iscsi.org>,
Ming Lei <ming.lei@canonical.com>,
linux-fsdevel@vger.kernel.org, target-devel@vger.kernel.org
Subject: switch loop and target to use ITER_BVEC iov_iter V2
Date: Sun, 25 Jan 2015 21:11:57 +0100 [thread overview]
Message-ID: <1422216722-27786-1-git-send-email-hch@lst.de> (raw)
This series adds two new helpers to easily read from and write to
arbitrary iov_iter structures and switches the loop driver and target file
backend to use those with bio_vecs.
Using bio_vecs directly avoids the need to kmap individual elements in
the callers, which is epecially important in the target driver, and also
gets rid of the horrible splice code abuse hack in the loop driver.
Changes since V1:
- rebase ontop of viro/for-next
- changed the helpers to read/write any iov_iter, and use
iov_iter_bvec to build those
- return -EINVAL if ->read_iter/->write_iter aren't present
instead of -EBADFD
- use kcalloc in the target patch
- add a patch to rewrite the target WRITE SAME emulation
next reply other threads:[~2015-01-25 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 20:11 Christoph Hellwig [this message]
2015-01-25 20:11 ` [PATCH 1/5] new helper: iov_iter_bvec() Christoph Hellwig
2015-01-25 20:11 ` [PATCH 2/5] fs: add vfs_iter_{read,write} helpers Christoph Hellwig
2015-01-25 20:12 ` [PATCH 3/5] loop: convert to vfs_iter_read/write Christoph Hellwig
2015-01-25 20:12 ` [PATCH 4/5] target: use vfs_iter_read/write in fd_do_rw Christoph Hellwig
2015-01-25 20:12 ` [PATCH 5/5] target: rewrite fd_execute_write_same Christoph Hellwig
2015-01-26 5:10 ` switch loop and target to use ITER_BVEC iov_iter V2 Al Viro
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=1422216722-27786-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).