On Mon, 2009-01-05 at 21:32 +1100, Nick Piggin wrote: > On Saturday 03 January 2009 06:38:07 Chris Mason wrote: > > The extent_map and extent_buffer code was also intended for generic use. > > It needs some love and care (making it work for blocksize != pagesize) > > before I'd suggest moving it out of fs/btrfs. > > I'm yet to be convinced it is a good idea to use extents for this. Been a > long time since we visited the issue, but when you converted ext2 to use > the extent mapping stuff, it actually went slower, and complexity went up > a lot (IIRC possibly required allocations in the writeback path). > > > So I think it is a fine idea to live in btrfs until it is more proven and > found useful elsewhere. It has gotten faster since then, but it makes sense to wait on moving extent_* code. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
