From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
tytso@mit.edu, Kyle McMartin <kyle@mcmartin.ca>,
linux-parisc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
James.Bottomley@suse.de, linux-arch@vger.kernel.org,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [git patches] xfs and block fixes for virtually indexed arches
Date: Thu, 17 Dec 2009 12:51:20 -0500 [thread overview]
Message-ID: <20091217175120.GA5741@infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0912170928310.15740@localhost.localdomain>
On Thu, Dec 17, 2009 at 09:42:15AM -0800, Linus Torvalds wrote:
> > Which is exactly what the XFS code does. Pages are allocated manually
> > and we store pointers to the page struct that later get added to the
> > bio.
>
> Hmm. The BIO interface that the patch-series changes (bio_map_kern)
> doesn't work that way. It takes a "buf, len" kind of thing. That's what
> I'm complaining about.
Indeed, the "block: permit I/O to vmalloc/vmap kernel pages" does what
you complain about. But the series doesn't actually add a user for
that. What it does in XFS is quite a bit of black magic, too - but only
with the new cache coherence calls that are noops on architectures with
physically indexed caches.
> Well, they clearly are _after_ this series, since that's what all those
> changes to __bio_map_kernel() and bio_map_kern_endio() are all about.
>
> So I believe you when you say that XFS perhaps does everything right - I
> just think that the patch series in question actually makes things worse,
> exactly because it is starting to use virtual addresses.
I'm not entirely sure why James added those, but XFS doesn't actually
use bio_map_kern.
> And I really think that would be all much more properly done at the
> _caller_ level, not by the BIO layer.
>
> You must have some locking and allocation etc logic at the caller anyway,
> why doesn't _that_ level just do the flushing or invalidation?
http://git.kernel.org/?p=linux/kernel/git/kyle/parisc-2.6.git;a=commitdiff;h=56c8214b842324e94aa88012010b0f1f9847daec
does it in the caller level. Not exactly in a beautiful way, but who
am I complain as I'm already lost in our mess of cache coherency APIs.
> IOW, I'm perfectly happy with the patch to fs/xfs/linux-2.6/xfs_buf.c.
> That one still seems to use 'bio_add_page()' with a regular 'struct page'.
>
> But the fs/bio.c patch looks like just total and utter crap to me, and is
> the reason I refuse to pull this series.
Kyle/James, can you regenerate the tree without that patch included?
next prev parent reply other threads:[~2009-12-17 17:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091216043618.GB9104@hera.kernel.org>
2009-12-17 13:22 ` [git patches] xfs and block fixes for virtually indexed arches Kyle McMartin
2009-12-17 13:22 ` Kyle McMartin
2009-12-17 13:25 ` Christoph Hellwig
2009-12-17 16:16 ` Linus Torvalds
2009-12-17 16:30 ` tytso
2009-12-17 16:46 ` Linus Torvalds
2009-12-17 16:46 ` Linus Torvalds
2009-12-17 17:07 ` Christoph Hellwig
2009-12-17 17:07 ` Christoph Hellwig
2009-12-17 17:42 ` Linus Torvalds
2009-12-17 17:51 ` Christoph Hellwig [this message]
2009-12-17 17:51 ` Christoph Hellwig
2009-12-17 18:08 ` Russell King
2009-12-17 18:08 ` Russell King
2009-12-17 18:17 ` Linus Torvalds
2009-12-17 18:17 ` Linus Torvalds
2009-12-19 18:33 ` Ralf Baechle
2009-12-19 18:33 ` Ralf Baechle
2009-12-21 17:14 ` James Bottomley
2009-12-17 17:39 ` tytso
2009-12-17 17:39 ` tytso
2009-12-17 17:51 ` Linus Torvalds
2009-12-17 19:36 ` Jens Axboe
2009-12-17 19:36 ` Jens Axboe
2009-12-17 23:57 ` James Bottomley
2009-12-17 23:57 ` James Bottomley
2009-12-18 1:00 ` FUJITA Tomonori
2009-12-18 2:44 ` Dave Chinner
2009-12-18 2:44 ` Dave Chinner
2009-12-18 3:51 ` FUJITA Tomonori
2009-12-18 3:51 ` FUJITA Tomonori
2009-12-18 7:10 ` James Bottomley
2009-12-18 7:08 ` James Bottomley
2009-12-18 9:34 ` FUJITA Tomonori
2009-12-18 10:01 ` James Bottomley
2009-12-18 10:01 ` James Bottomley
2009-12-18 10:24 ` FUJITA Tomonori
2009-12-18 10:30 ` James Bottomley
2009-12-18 12:00 ` Dave Chinner
2009-12-18 12:00 ` Dave Chinner
2009-12-18 0:21 ` FUJITA Tomonori
2009-12-18 14:17 ` tytso
2009-12-18 14:17 ` tytso
2009-12-21 8:53 ` FUJITA Tomonori
2009-12-17 17:10 ` Christoph Hellwig
2009-12-17 17:10 ` Christoph Hellwig
2009-12-17 17:33 ` tytso
2009-12-17 17:33 ` tytso
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=20091217175120.GA5741@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@suse.de \
--cc=jens.axboe@oracle.com \
--cc=kyle@mcmartin.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).