From: Zach Brown <zach.brown@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
Benjamin LaHaise <bcrl@kvack.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [Patch] vectored aio: IO_CMD_P{READ,WRITE}V and fops->aio_{read,write}v
Date: Sun, 06 Nov 2005 21:00:50 -0800 [thread overview]
Message-ID: <436EDF82.8070402@oracle.com> (raw)
In-Reply-To: <20051107045300.GA17265@lst.de>
Christoph Hellwig wrote:
> On Fri, Nov 04, 2005 at 05:03:58PM -0800, Zach Brown wrote:
>> If we're going down this path, and find ourselves touching every vectored
>> implementation in the world, I wonder if we shouldn't consider that iovec
>> container. The desire is to avoid the duplicated iovec walking that happens at
>> the various layers by storing the result of a single walk. An ext3 O_DIRECT
>> write walks the iovec no fewer than 7 times:
> As we discussed a while ago adding some kinds of fs_iovec or kern_iovec
> structure that records useful addition information could help this.
> Would you mind prototyping it?
Yeah, I have a patch that I've been kicking around. It's working out
pretty well, though there are some kinks to work around. Nothing fatal
so far. I realized when I finally sat down to it that we can just or
together the ptr/len bits and cache them in the structure to help lower
layers with the alignment checks they're currently doing.
> The nice part about the consolidation work I'm doing now is that we'd
> need to touch much fewer places for this than before.
Cool.
I'll try and send something out the next few days.
- z
prev parent reply other threads:[~2005-11-07 5:00 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
2005-11-05 1:03 ` Zach Brown
2005-11-07 4:53 ` Christoph Hellwig
2005-11-07 5:00 ` Zach Brown [this message]
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=436EDF82.8070402@oracle.com \
--to=zach.brown@oracle.com \
--cc=akpm@osdl.org \
--cc=bcrl@kvack.org \
--cc=hch@lst.de \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@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