linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	chris.mason@oracle.com, david@fromorbit.com, hch@infradead.org,
	akpm@linux-foundation.org, jack@suse.cz,
	yanmin_zhang@linux.intel.com, damien.wyart@free.fr
Subject: Re: [PATCH 0/11] Per-bdi writeback flusher threads v8
Date: Wed, 27 May 2009 14:47:46 +0200	[thread overview]
Message-ID: <20090527124746.GI11363@kernel.dk> (raw)
In-Reply-To: <1243428088.2769.12.camel@localhost.localdomain>

On Wed, May 27 2009, Richard Kennedy wrote:
> On Wed, 2009-05-27 at 11:41 +0200, Jens Axboe wrote:
> > Hi,
> > 
> > Here's the 8th version of the writeback patches. Changes since v7:
> > 
> > - Fold the "include default_backing_dev_info in writeback" patch into
> >   the core, we should just do it from the beginning.
> > - More series cleanup, I think it should be mostly complete now. No
> >   hunks are split between patches now (things like comments for
> >   functions added earlier, and so on).
> > - Fix hang with calling bdi_wait_on_work_clear() inside the bdi_lock
> >   mutex when the default wb thread had exited.
> > - Fix hang with queuing work on exited wb thread, it would have no
> >   receipients since the default wb thread wrongly cleared the bit
> >   from the register mask on exit. It must be persistent, which is
> >   why it gets initialized on bdi_register() already.
> > 
> > For ease of patching, I've put the full diff here:
> > 
> >   http://kernel.dk/writeback-v8.patch
> > 
> > and also stored this in a writeback-v7 branch that will not change,
> > you can pull that into Linus tree from here:
> > 
> >   git://git.kernel.dk/linux-2.6-block.git writeback-v8
> > 
> >  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          |   24 -
> >  b/fs/buffer.c                 |    2 
> >  b/fs/char_dev.c               |    1 
> >  b/fs/configfs/inode.c         |    1 
> >  b/fs/fs-writeback.c           |  807 +++++++++++++++++++++++++++-------
> >  b/fs/fuse/inode.c             |    1 
> >  b/fs/hugetlbfs/inode.c        |    1 
> >  b/fs/nfs/client.c             |    1 
> >  b/fs/ntfs/super.c             |   33 -
> >  b/fs/ocfs2/dlm/dlmfs.c        |    1 
> >  b/fs/ramfs/inode.c            |    1 
> >  b/fs/super.c                  |    3 
> >  b/fs/sync.c                   |    2 
> >  b/fs/sysfs/inode.c            |    1 
> >  b/fs/ubifs/super.c            |    1 
> >  b/include/linux/backing-dev.h |   74 +++
> >  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            |  476 +++++++++++++++++++-
> >  b/mm/page-writeback.c         |  151 ------
> >  b/mm/swap_state.c             |    1 
> >  b/mm/vmscan.c                 |    2 
> >  mm/pdflush.c                  |  269 -----------
> >  28 files changed, 1248 insertions(+), 637 deletions(-)
> > 
> Hi Jens,
> 
> This is working nicely for me. It's successfully built a kernel with no
> problems at all, so you've fixed the earlier problem I had.
> 
> Early fio tests writing to 2 disks at the same time indicate that it's
> faster too. But there's a fair amount of variability so I will run more
> tests & see what the trend really is.

That's good to hear, thanks for testing! Do let me know if you run into
anything suspicious later on.

-- 
Jens Axboe


  reply	other threads:[~2009-05-27 12:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  9:41 [PATCH 0/11] Per-bdi writeback flusher threads v8 Jens Axboe
2009-05-27  9:41 ` [PATCH 01/11] ntfs: remove old debug check for dirty data in ntfs_put_super() Jens Axboe
2009-05-27  9:41 ` [PATCH 02/11] btrfs: properly register fs backing device Jens Axboe
2009-05-27  9:41 ` [PATCH 03/11] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-05-27  9:41 ` [PATCH 04/11] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-05-27 11:11   ` Peter Zijlstra
2009-05-27 11:24     ` Jens Axboe
2009-05-27 15:14   ` Jan Kara
2009-05-27 17:50     ` Jens Axboe
2009-05-28 14:45       ` Jan Kara
2009-05-27  9:41 ` [PATCH 05/11] writeback: get rid of pdflush completely Jens Axboe
2009-05-27  9:41 ` [PATCH 06/11] writeback: separate the flushing state/task from the bdi Jens Axboe
2009-05-27  9:41 ` [PATCH 07/11] writeback: support > 1 flusher thread per bdi Jens Axboe
2009-05-28  9:27   ` Jan Kara
2009-05-28 10:40     ` Jens Axboe
2009-05-28 12:43       ` Jan Kara
2009-05-28 12:53         ` Jens Axboe
2009-05-28 13:58           ` Jan Kara
2009-05-27  9:41 ` [PATCH 08/11] writeback: allow sleepy exit of default writeback task Jens Axboe
2009-05-27  9:41 ` [PATCH 09/11] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-05-27  9:41 ` [PATCH 10/11] writeback: add name to backing_dev_info Jens Axboe
2009-05-27  9:41 ` [PATCH 11/11] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-05-27 12:41 ` [PATCH 0/11] Per-bdi writeback flusher threads v8 Richard Kennedy
2009-05-27 12:47   ` Jens Axboe [this message]
2009-05-27 14:47 ` Theodore Tso
2009-05-27 15:05   ` Jens Axboe
2009-05-27 17:53   ` Theodore Tso
2009-05-27 17:57     ` Jens Axboe
2009-05-27 17:58     ` Theodore Tso
2009-05-27 18:14       ` Jens Axboe
2009-05-27 19:15         ` Jens Axboe
2009-05-27 19:45           ` Jens Axboe
2009-05-28  0:49             ` Theodore Tso
2009-05-28  9:28               ` Jan Kara
2009-05-28  9:36                 ` Jens Axboe
2009-05-28 15:23                 ` Eric W. Biederman
2009-05-28 19:32                   ` Theodore Tso
2009-05-28 19:38                     ` Christoph Hellwig

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=20090527124746.GI11363@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=damien.wyart@free.fr \
    --cc=david@fromorbit.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).