From: Sedat Dilek <sedat.dilek@gmail.com>
To: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Maxim V. Patlasov" <mpatlasov@parallels.com>,
Zach Brown <zab@zabbo.net>
Subject: Re: [PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec
Date: Wed, 31 Dec 2014 21:38:02 +0100 [thread overview]
Message-ID: <CA+icZUV17qR-kBRnYa+r0DfchQ0QtaBy-6c3f3QuXn0EGwuJzQ@mail.gmail.com> (raw)
In-Reply-To: <1374774659-13121-1-git-send-email-dave.kleikamp@oracle.com>
On Thu, Jul 25, 2013 at 7:50 PM, Dave Kleikamp <dave.kleikamp@oracle.com> wrote:
> This patch series adds a kernel interface to fs/aio.c so that kernel code can
> issue concurrent asynchronous IO to file systems. It adds an aio command and
> file system methods which specify io memory with pages instead of userspace
> addresses.
>
> This series was written to reduce the current overhead loop imposes by
> performing synchronus buffered file system IO from a kernel thread. These
> patches turn loop into a light weight layer that translates bios into iocbs.
>
> It introduces new file ops, read_iter() and write_iter(), that replace the
> aio_read() and aio_write() operations. The iov_iter structure can now contain
> either a user-space iovec or a kernel-space bio_vec. Since it would be
> overly complicated to replace every instance of aio_read() and aio_write(),
> the old operations are not removed, but file systems implementing the new
> ones need not keep the old ones.
>
> Verion 8 is little changed from Version 7 that I send out in March, just
> updated to the latest kernel. These patches apply to 3.11-rc2 and can
> also be found at:
>
> git://github.com/kleikamp/linux-shaggy.git aio_loop
>
What has happened to that aio_loop patchset?
Is it in Linux-next?
( /me started to play with "block: loop: convert to blk-mq (v3)", so I
recalled this other improvement. )
- Sedat -
> Asias He (1):
> block_dev: add support for read_iter, write_iter
>
> Dave Kleikamp (22):
> iov_iter: iov_iter_copy_from_user() should use non-atomic copy
> iov_iter: add __iovec_copy_to_user()
> fuse: convert fuse to use iov_iter_copy_[to|from]_user
> iov_iter: ii_iovec_copy_to_user should pre-fault user pages
> dio: Convert direct_IO to use iov_iter
> dio: add bio_vec support to __blockdev_direct_IO()
> aio: add aio_kernel_() interface
> aio: add aio support for iov_iter arguments
> fs: create file_readable() and file_writable() functions
> fs: use read_iter and write_iter rather than aio_read and aio_write
> fs: add read_iter and write_iter to several file systems
> ocfs2: add support for read_iter and write_iter
> ext4: add support for read_iter and write_iter
> nfs: add support for read_iter, write_iter
> nfs: simplify swap
> btrfs: add support for read_iter and write_iter
> xfs: add support for read_iter and write_iter
> gfs2: Convert aio_read/write ops to read/write_iter
> udf: convert file ops from aio_read/write to read/write_iter
> afs: add support for read_iter and write_iter
> ecrpytfs: Convert aio_read/write ops to read/write_iter
> ubifs: convert file ops from aio_read/write to read/write_iter
>
> Hugh Dickins (1):
> tmpfs: add support for read_iter and write_iter
>
> Zach Brown (9):
> iov_iter: move into its own file
> iov_iter: add copy_to_user support
> iov_iter: hide iovec details behind ops function pointers
> iov_iter: add bvec support
> iov_iter: add a shorten call
> iov_iter: let callers extract iovecs and bio_vecs
> fs: pull iov_iter use higher up the stack
> bio: add bvec_length(), like iov_length()
> loop: use aio to perform io on the underlying file
>
> Documentation/filesystems/Locking | 6 +-
> Documentation/filesystems/vfs.txt | 12 +-
> drivers/block/loop.c | 148 ++++++++----
> drivers/char/raw.c | 4 +-
> drivers/mtd/nand/nandsim.c | 4 +-
> drivers/usb/gadget/storage_common.c | 4 +-
> fs/9p/vfs_addr.c | 12 +-
> fs/9p/vfs_file.c | 8 +-
> fs/Makefile | 2 +-
> fs/adfs/file.c | 4 +-
> fs/affs/file.c | 4 +-
> fs/afs/file.c | 4 +-
> fs/afs/internal.h | 3 +-
> fs/afs/write.c | 9 +-
> fs/aio.c | 152 ++++++++++++-
> fs/bad_inode.c | 14 ++
> fs/bfs/file.c | 4 +-
> fs/block_dev.c | 27 ++-
> fs/btrfs/file.c | 42 ++--
> fs/btrfs/inode.c | 63 +++---
> fs/ceph/addr.c | 3 +-
> fs/cifs/file.c | 4 +-
> fs/direct-io.c | 223 +++++++++++++------
> fs/ecryptfs/file.c | 15 +-
> fs/exofs/file.c | 4 +-
> fs/ext2/file.c | 4 +-
> fs/ext2/inode.c | 8 +-
> fs/ext3/file.c | 4 +-
> fs/ext3/inode.c | 15 +-
> fs/ext4/ext4.h | 3 +-
> fs/ext4/file.c | 34 +--
> fs/ext4/indirect.c | 16 +-
> fs/ext4/inode.c | 23 +-
> fs/f2fs/data.c | 4 +-
> fs/f2fs/file.c | 4 +-
> fs/fat/file.c | 4 +-
> fs/fat/inode.c | 10 +-
> fs/fuse/cuse.c | 10 +-
> fs/fuse/file.c | 90 ++++----
> fs/fuse/fuse_i.h | 5 +-
> fs/gfs2/aops.c | 7 +-
> fs/gfs2/file.c | 21 +-
> fs/hfs/inode.c | 11 +-
> fs/hfsplus/inode.c | 10 +-
> fs/hostfs/hostfs_kern.c | 4 +-
> fs/hpfs/file.c | 4 +-
> fs/internal.h | 4 +
> fs/iov-iter.c | 411 ++++++++++++++++++++++++++++++++++
> fs/jffs2/file.c | 8 +-
> fs/jfs/file.c | 4 +-
> fs/jfs/inode.c | 7 +-
> fs/logfs/file.c | 4 +-
> fs/minix/file.c | 4 +-
> fs/nfs/direct.c | 302 ++++++++++++++++---------
> fs/nfs/file.c | 33 ++-
> fs/nfs/internal.h | 4 +-
> fs/nfs/nfs4file.c | 4 +-
> fs/nilfs2/file.c | 4 +-
> fs/nilfs2/inode.c | 8 +-
> fs/ocfs2/aops.c | 8 +-
> fs/ocfs2/aops.h | 2 +-
> fs/ocfs2/file.c | 55 ++---
> fs/ocfs2/ocfs2_trace.h | 6 +-
> fs/omfs/file.c | 4 +-
> fs/ramfs/file-mmu.c | 4 +-
> fs/ramfs/file-nommu.c | 4 +-
> fs/read_write.c | 78 +++++--
> fs/reiserfs/file.c | 4 +-
> fs/reiserfs/inode.c | 7 +-
> fs/romfs/mmap-nommu.c | 2 +-
> fs/sysv/file.c | 4 +-
> fs/ubifs/file.c | 12 +-
> fs/udf/file.c | 13 +-
> fs/udf/inode.c | 10 +-
> fs/ufs/file.c | 4 +-
> fs/xfs/xfs_aops.c | 13 +-
> fs/xfs/xfs_file.c | 51 ++---
> include/linux/aio.h | 20 +-
> include/linux/bio.h | 8 +
> include/linux/blk_types.h | 2 -
> include/linux/fs.h | 165 ++++++++++++--
> include/linux/nfs_fs.h | 13 +-
> include/uapi/linux/aio_abi.h | 2 +
> include/uapi/linux/loop.h | 1 +
> mm/filemap.c | 433 ++++++++++++++----------------------
> mm/page_io.c | 15 +-
> mm/shmem.c | 61 ++---
> 87 files changed, 1862 insertions(+), 1002 deletions(-)
> create mode 100644 fs/iov-iter.c
>
> --
> 1.8.3.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-31 20:38 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 17:50 [PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 01/33] iov_iter: move into its own file Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 02/33] iov_iter: iov_iter_copy_from_user() should use non-atomic copy Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 03/33] iov_iter: add copy_to_user support Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 04/33] iov_iter: add __iovec_copy_to_user() Dave Kleikamp
[not found] ` <1374774659-13121-1-git-send-email-dave.kleikamp-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-07-25 17:50 ` [PATCH V8 05/33] fuse: convert fuse to use iov_iter_copy_[to|from]_user Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 06/33] iov_iter: hide iovec details behind ops function pointers Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 07/33] iov_iter: ii_iovec_copy_to_user should pre-fault user pages Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 08/33] iov_iter: add bvec support Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 09/33] iov_iter: add a shorten call Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 10/33] iov_iter: let callers extract iovecs and bio_vecs Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 11/33] dio: Convert direct_IO to use iov_iter Dave Kleikamp
2013-08-23 15:48 ` Geert Uytterhoeven
2013-07-25 17:50 ` [PATCH V8 12/33] dio: add bio_vec support to __blockdev_direct_IO() Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 13/33] fs: pull iov_iter use higher up the stack Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 14/33] aio: add aio_kernel_() interface Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 15/33] aio: add aio support for iov_iter arguments Dave Kleikamp
2013-08-21 13:55 ` Benjamin LaHaise
2013-08-30 20:05 ` Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 16/33] bio: add bvec_length(), like iov_length() Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 17/33] loop: use aio to perform io on the underlying file Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 18/33] fs: create file_readable() and file_writable() functions Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 19/33] fs: use read_iter and write_iter rather than aio_read and aio_write Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 20/33] fs: add read_iter and write_iter to several file systems Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 21/33] ocfs2: add support for read_iter and write_iter Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 22/33] ext4: " Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 23/33] nfs: add support for read_iter, write_iter Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 24/33] nfs: simplify swap Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 25/33] btrfs: add support for read_iter and write_iter Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 26/33] block_dev: add support for read_iter, write_iter Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 27/33] xfs: add support for read_iter and write_iter Dave Kleikamp
2013-07-26 11:51 ` Dave Chinner
2013-07-25 17:50 ` [PATCH V8 28/33] gfs2: Convert aio_read/write ops to read/write_iter Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 29/33] udf: convert file ops from aio_read/write " Dave Kleikamp
2013-07-25 21:34 ` Jan Kara
2013-07-25 17:50 ` [PATCH V8 30/33] afs: add support for read_iter and write_iter Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 31/33] ecrpytfs: Convert aio_read/write ops to read/write_iter Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 32/33] ubifs: convert file ops from aio_read/write " Dave Kleikamp
2013-07-25 17:50 ` [PATCH V8 33/33] tmpfs: add support for read_iter and write_iter Dave Kleikamp
2013-07-30 21:28 ` [PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec Andrew Morton
2013-07-31 0:43 ` Dave Chinner
2013-07-31 6:40 ` Sedat Dilek
2013-07-31 8:41 ` Sedat Dilek
2013-07-31 11:22 ` Sedat Dilek
2013-07-31 9:51 ` Maxim Patlasov
2013-08-01 8:58 ` Christoph Hellwig
2013-08-01 13:04 ` Dave Kleikamp
2013-08-02 10:48 ` Christoph Hellwig
2013-08-20 13:00 ` Christoph Hellwig
2013-08-20 19:13 ` Dave Kleikamp
2013-08-21 0:14 ` Stephen Rothwell
2013-08-21 5:35 ` Sedat Dilek
2013-08-20 22:46 ` Andrew Morton
2013-08-21 13:02 ` Benjamin LaHaise
2013-08-21 16:30 ` Dave Kleikamp
2013-08-21 16:39 ` Benjamin LaHaise
2013-08-21 17:12 ` Dave Kleikamp
2013-08-21 19:30 ` Andrew Morton
2013-08-21 20:24 ` Benjamin LaHaise
2013-10-14 15:07 ` Christoph Hellwig
2013-10-14 21:29 ` Benjamin LaHaise
2013-10-15 16:55 ` Christoph Hellwig
2013-10-15 17:14 ` Benjamin LaHaise
2013-10-15 17:18 ` Christoph Hellwig
2013-10-15 17:53 ` Dave Kleikamp
2014-12-31 20:38 ` Sedat Dilek [this message]
2014-12-31 21:52 ` Dave Kleikamp
2014-12-31 22:35 ` Sedat Dilek
2015-01-01 0:52 ` Ming Lei
2015-01-05 19:24 ` Maxim Patlasov
2015-01-06 13:18 ` Ming Lei
2015-01-10 16:51 ` Ming Lei
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=CA+icZUV17qR-kBRnYa+r0DfchQ0QtaBy-6c3f3QuXn0EGwuJzQ@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dave.kleikamp@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatlasov@parallels.com \
--cc=zab@zabbo.net \
/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).