writeback: move dirty inodes from super_block to backing_dev_info
authorJens Axboe <jens.axboe@oracle.com>
Wed, 2 Sep 2009 07:19:46 +0000 (09:19 +0200)
committerJens Axboe <jens.axboe@oracle.com>
Fri, 11 Sep 2009 07:20:25 +0000 (09:20 +0200)
commit66f3b8e2e103a0b93b945764d98e9ba46cb926dd
tree442bf5664214f0a1448e4010b09868cc58fdd3d1
parentd8a8559cd7a9ccac98d5f6f13297a2ff68a43627
writeback: move dirty inodes from super_block to backing_dev_info

This is a first step at introducing per-bdi flusher threads. We should
have no change in behaviour, although sb_has_dirty_inodes() is now
ridiculously expensive, as there's no easy way to answer that question.
Not a huge problem, since it'll be deleted in subsequent patches.

Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
fs/fs-writeback.c
fs/super.c
include/linux/backing-dev.h
include/linux/fs.h
mm/backing-dev.c
mm/page-writeback.c