On Tue, Oct 05, 2010 at 11:29:55AM -0400, Boaz Harrosh wrote: > If you are right and inode->i_mapping.backing_dev_info will only be used for bdev > inodes, then I prefer if it would be NULL by default and not pointing to > &default_backing_dev_info. Will that be fixed as well? It's been pointing to default_backing_dev_info since long before we got the per-bdi writeback. Once the writeback bits are're back to what we used the BDI for before: - set VM readahead parameters - deal with per-backingdev congestion/unplugging - a couple of VM statistics in general all these really should point to the same for a normal filesystem, and at least point to the same in a group even for "strange" filesystems that have multiple backing devices. The BDI still is a rather strangely defined beast, and so far all my attempts to make sense of it have failed. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
