[PATCH 0/10] Per-bdi writeback flusher threads v12

From: Jens Axboe
Date: Thu Jun 25 2009 - 06:42:32 EST


Hi,

Here's the 12th version of the writeback patches. Changes since v11:

- Fixup kthread_run() error check, it should use IS_ERR() instead of
checking for NULL. Thanks Andrew.
- Fix a silly buglet that would quickly respawn otherwise idle threads
once they had exited. This was due to an inverted if test. Didn't cause
any harm except potentially too many writeback threads setting idle in
the system.
- Integrate kupdate periodic writeback with the explicit writeback. Cleans
that part up.
- Update to 2.6.31-rc1. With the recent patches from viro and hch, v11
did not apply cleanly at all to 2.6.31-rc1.

For ease of patching, I've put the full diff here:

http://kernel.dk/writeback-v12.patch

and also stored this in a writeback-v12 branch that will not change,
you can pull that into Linus tree from here:

git://git.kernel.dk/linux-2.6-block.git writeback-v12

Please test and report results/interesting finds. Thanks! The target
for this patchset is 2.6.32 and it'll be sitting (and has been for the past
week approx) in -next until then.

b/block/blk-core.c | 1
b/drivers/block/aoe/aoeblk.c | 1
b/drivers/char/mem.c | 1
b/fs/btrfs/disk-io.c | 1
b/fs/buffer.c | 2
b/fs/char_dev.c | 1
b/fs/configfs/inode.c | 1
b/fs/fs-writeback.c | 775 +++++++++++++++++++++++++++-------
b/fs/fuse/inode.c | 1
b/fs/hugetlbfs/inode.c | 1
b/fs/nfs/client.c | 1
b/fs/ocfs2/dlm/dlmfs.c | 1
b/fs/ramfs/inode.c | 1
b/fs/super.c | 3
b/fs/sysfs/inode.c | 1
b/fs/ubifs/super.c | 1
b/include/linux/backing-dev.h | 71 +++
b/include/linux/fs.h | 11
b/include/linux/writeback.h | 15
b/kernel/cgroup.c | 1
b/mm/Makefile | 2
b/mm/backing-dev.c | 533 +++++++++++++++++++++++
b/mm/page-writeback.c | 157 ------
b/mm/swap_state.c | 1
b/mm/vmscan.c | 2
mm/pdflush.c | 269 -----------
26 files changed, 1259 insertions(+), 596 deletions(-)

--
Jens Axboe


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/