linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: chris.mason@oracle.com, david@fromorbit.com, hch@infradead.org,
	akpm@linux-foundation.org, jack@suse.cz,
	yanmin_zhang@linux.intel.com, richard@rsk.demon.co.uk,
	damien.wyart@free.fr, fweisbec@gmail.com, Alan.Brunelle@hp.com
Subject: [PATCH 0/10] Per-bdi writeback flusher threads v11
Date: Wed, 17 Jun 2009 13:07:12 +0200	[thread overview]
Message-ID: <1245236842-3141-1-git-send-email-jens.axboe@oracle.com> (raw)

Hi,

Here's the 11th version of the writeback patches. Changes since v10:

- I think this finally fixes the one show stopper issue I was aware
  of. This is the one that Yanmin Zhang reported and which has plagued
  this patch series for some time. Basically it was due to a race
  between work queueing and exited tasks. I cleaned up this part while
  fixing the bug.
- The three prep patches are now merged, so they have been deleted.
- Updated to current -git.

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

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

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

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

Please test and report results/interesting finds. Thanks! I hope to merge
this work sooner rather than later, so please do give it a good beating.

 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           |  812 +++++++++++++++++++++++++++-------
 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 |   72 ++-
 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            |  530 +++++++++++++++++++++-
 b/mm/page-writeback.c         |  157 ------
 b/mm/swap_state.c             |    1 
 b/mm/vmscan.c                 |    2 
 mm/pdflush.c                  |  269 -----------
 26 files changed, 1293 insertions(+), 597 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2009-06-17 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 11:07 Jens Axboe [this message]
2009-06-17 11:07 ` [PATCH 01/10] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-06-17 11:07 ` [PATCH 02/10] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-06-17 11:07 ` [PATCH 03/10] writeback: get rid of pdflush completely Jens Axboe
2009-06-17 11:07 ` [PATCH 04/10] writeback: separate the flushing state/task from the bdi Jens Axboe
2009-06-17 11:07 ` [PATCH 05/10] writeback: support > 1 flusher thread per bdi Jens Axboe
2009-06-17 11:07 ` [PATCH 06/10] writeback: allow sleepy exit of default writeback task Jens Axboe
2009-06-17 11:07 ` [PATCH 07/10] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-06-17 11:07 ` [PATCH 08/10] writeback: add name to backing_dev_info Jens Axboe
2009-06-17 11:07 ` [PATCH 09/10] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-06-17 11:07 ` [PATCH 10/10] writeback: use spin_trylock() in bdi_writeback_all() for WB_SYNC_NONE Jens Axboe
2009-06-17 12:18 ` 2.6.30 backport (Was "Re: [PATCH 0/10] Per-bdi writeback flusher threads v11") 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=1245236842-3141-1-git-send-email-jens.axboe@oracle.com \
    --to=jens.axboe@oracle.com \
    --cc=Alan.Brunelle@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=damien.wyart@free.fr \
    --cc=david@fromorbit.com \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@rsk.demon.co.uk \
    --cc=yanmin_zhang@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).