All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org, hch@infradead.org
Subject: merging the per-bdi writeback patchset
Date: Tue, 23 Jun 2009 10:11:56 +0200	[thread overview]
Message-ID: <20090623081156.GT31415@kernel.dk> (raw)

Hi,

Things are looking good for this patchset and it's been in -next for
almost a week without any reports of problems. So I'd like to merge it
for 2.6.31 if at all possible. Any objections?

This was the last posting of the patchset:

http://lkml.org/lkml/2009/6/17/143

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

Jens Axboe (10):
      writeback: move dirty inodes from super_block to backing_dev_info
      writeback: switch to per-bdi threads for flushing data
      writeback: get rid of pdflush completely
      writeback: separate the flushing state/task from the bdi
      writeback: support > 1 flusher thread per bdi
      writeback: allow sleepy exit of default writeback task
      writeback: add some debug inode list counters to bdi stats
      writeback: add name to backing_dev_info
      writeback: check for registered bdi in flusher add and inode dirty
      writeback: use spin_trylock() in bdi_writeback_all() for WB_SYNC_NONE

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

-- 
Jens Axboe


             reply	other threads:[~2009-06-23  8:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  8:11 Jens Axboe [this message]
2009-06-23  8:48 ` merging the per-bdi writeback patchset Andrew Morton
2009-06-23  8:55   ` Jens Axboe
2009-06-23 10:28     ` KOSAKI Motohiro
2009-06-23 10:56       ` Jens Axboe
2009-06-23 11:19         ` KOSAKI Motohiro
2009-06-23 11:28           ` Jens Axboe
2009-06-23 11:44             ` KOSAKI Motohiro
2009-06-23 15:01     ` Andrew Morton
2009-06-24 10:04       ` Jens Axboe
2009-06-23 11:09 ` Christoph Hellwig
2009-06-23 11:12   ` Jens Axboe
2009-06-23 11:17     ` Christoph Hellwig
2009-06-23 11:52       ` Jens Axboe
2009-06-23 12:20         ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090623081156.GT31415@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.