On Wed, 2009-11-18 at 23:15 +0900, FUJITA Tomonori wrote: > On Wed, 18 Nov 2009 08:50:40 -0500 > James Bottomley <James.Bottomley@xxxxxxx> wrote: > > > On Wed, 2009-11-18 at 19:10 +0900, FUJITA Tomonori wrote: > > > On Tue, 17 Nov 2009 11:03:51 -0600 > > > James Bottomley <James.Bottomley@xxxxxxx> wrote: > > > > > > > This updates bio_map_kern() to check for pages in the vmalloc address > > > > range and call the new kernel flushing APIs if the are. This should > > > > allow any kernel user to pass a vmalloc/vmap area to block. > > > > > > > > Signed-off-by: James Bottomley <James.Bottomley@xxxxxxx> > > > > --- > > > > fs/bio.c | 20 ++++++++++++++++++-- > > > > 1 files changed, 18 insertions(+), 2 deletions(-) > > > > > > Do we need this? > > > > > > Buffers that xfs_buf.c passes to block doesn't go to bio_map_kern()? > > > > For completeness, yes ... because xfs *should* be passing its buffers to > > bio_map_kern() ... it just happens to roll its own. > > Ok, you mean that we will convert XFS to use bio_map_kern(). > > But adding another trick to bio_map_kern() to handle a vmalloc/vmap > area is a good move? Only XFS do such, right? Well, it's more a question of how we want the Linux APIs to look. Should passing vmalloc/vmap areas into the I/O routines be wrong? Right at the moment it doesn't work but xfs is the only consumer. There are definite reasons to say yes: greater flexibility for handling large buffers which logging filesystems seem to need. My position is either xfs is right and we should handle them correctly (and hence all the APIs should handle them correctly including bio_map_kern) or xfs is wrong and we should try and make it work with current APIs (which would necessitate a large contiguous physical allocation ... with all the associated problems). I chose the former with this patch. James -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
