From: jim owens <jowens@hp.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC 00/12] btrfs core patches for direct I/O
Date: Wed, 06 Jan 2010 13:53:02 -0500 [thread overview]
Message-ID: <4B44DC0E.5050903@hp.com> (raw)
In-Reply-To: <87ocl7bgg0.fsf@basil.nowhere.org>
Andi Kleen wrote:
> jim owens <jowens@hp.com> writes:
>
>> The existing core code for pagecache
>> doesn't work for directio because the existing I/O routines depend
>> on peeking inside a struct page to get the valid btrfs inode info.
>> Sorry, no can do, we don't own that page. And rewriting the whole
>> pagecache I/O stack to eliminate dependence on struct page would
>> be too scary IMO.
>
> That would simply need another passed argument in a few strategic
> places, won't it? I can't imagine it would need a full "rewrite"
I should not have said "rewrite", it is the wrong word, and yes
some changes in some places would be easy.
jim
prev parent reply other threads:[~2010-01-06 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 21:11 [RFC 00/12] btrfs core patches for direct I/O jim owens
2010-01-06 11:50 ` Andi Kleen
2010-01-06 18:53 ` jim owens [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=4B44DC0E.5050903@hp.com \
--to=jowens@hp.com \
--cc=andi@firstfloor.org \
--cc=linux-btrfs@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