From: Christoph Hellwig <hch@lst.de>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
Benjamin LaHaise <bcrl@kvack.org>, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Patch] vectored aio: IO_CMD_P{READ,WRITE}V and fops->aio_{read,write}v
Date: Sat, 5 Nov 2005 01:24:06 +0100 [thread overview]
Message-ID: <20051105002406.GA11235@lst.de> (raw)
In-Reply-To: <20051102233020.27835.89951.sendpatchset@volauvent.pdx.zabbo.net>
On Wed, Nov 02, 2005 at 03:27:29PM -0800, Zach Brown wrote:
>
> vectored aio: IO_CMD_P{READ,WRITE}V and fops->aio_{read,write}v
>
> This adds IO_CMD_IO_CMD_P{READ,WRITE}V to let userspace specify buffers with
> iovecs. aio_{read,write}v file operations are then used by the AIO core to
> hand the iovecs to filesystems, a significant number of whom already implement
> their IO methods in terms of iovecs. It lets applications work with vectored
> file IO in single AIO operations instead of having to issue multiple AIO ops.
> This is of particular use with O_DIRECT when the iovecs are pushed all the way
> down to devices which are capable of scatter-gather DMA.
The aio.c portion looks nice. I'm not happy about the filesystems bits.
The last thing we want is another set of read/write file operations. So
as part of the patch (it'll probably grow into a series) we should
remove the aio non-vectored and maybe even the plain vectored
operations. Doing that will be a lot simpler after I finished sorting
out various bits of duplication in the generic read/write path. I've
sent the first patch for that to -fsdevel already, but there's a few
more to follow.
next prev parent reply other threads:[~2005-11-05 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 23:27 [Patch] vectored aio: IO_CMD_P{READ,WRITE}V and fops->aio_{read,write}v Zach Brown
2005-11-05 0:24 ` Christoph Hellwig [this message]
2005-11-05 1:03 ` Zach Brown
2005-11-07 4:53 ` Christoph Hellwig
2005-11-07 5:00 ` Zach Brown
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=20051105002406.GA11235@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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