[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1237749964-8343-1-git-send-email-jens.axboe@oracle.com>
Date: Sun, 22 Mar 2009 20:25:52 +0100
From: Jens Axboe <jens.axboe@...cle.com>
To: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Cc: chris.mason@...cle.com, david@...morbit.com, npiggin@...e.de,
hch@...radead.org, akpm@...ux-foundation.org
Subject: [PATCH 0/12] Per-bdi writeback flusher threads #2
Hi,
Second version of this patchset. Changes since last time:
- Rearranged the obvious and prep patches to be at the beginning
of the series. That's patches 1-3, they will go upstream for 2.6.30
since they are just cleanups.
- The other change is more interesting. It adds support for > 1 flusher
thread per bdi. Comments welcome, I'm particularly curious whether
the super_operation is the right place to add this or not. We'll also
need a few other changes, particularly I think that users of this will
want to provide their own generic_sync_wb_inodes() at least. Probably
along with their own variants of queue_io/requeue_io/redirty_tail() and
so on.
- Various little bug fixes.
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 | 3
b/fs/buffer.c | 2
b/fs/char_dev.c | 1
b/fs/configfs/inode.c | 1
b/fs/fs-writeback.c | 490 +++++++++++++++++++++++-----------
b/fs/fuse/inode.c | 1
b/fs/hugetlbfs/inode.c | 1
b/fs/nfs/client.c | 1
b/fs/ntfs/super.c | 32 --
b/fs/ocfs2/dlm/dlmfs.c | 1
b/fs/ramfs/inode.c | 1
b/fs/super.c | 14
b/fs/sync.c | 16 -
b/fs/sysfs/inode.c | 1
b/fs/ubifs/super.c | 1
b/include/linux/backing-dev.h | 62 ++++
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 | 429 +++++++++++++++++++++++++++++
b/mm/page-writeback.c | 140 ---------
mm/pdflush.c | 251 -----------------
b/mm/readahead.c | 25 -
b/mm/swap_state.c | 1
b/mm/vmscan.c | 2
29 files changed, 889 insertions(+), 619 deletions(-)
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists