linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Jens Axboe <jens.axboe@oracle.com>
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, richard@rsk.demon.co.uk,
	damien.wyart@free.fr, fweisbec@gmail.com, Alan.Brunelle@hp.com
Subject: Re: [PATCH 0/10] Per-bdi writeback flusher threads v12
Date: Mon, 29 Jun 2009 16:43:37 +0800	[thread overview]
Message-ID: <1246265017.2560.446.camel@ymzhang> (raw)
In-Reply-To: <1245926523-21959-1-git-send-email-jens.axboe@oracle.com>

On Thu, 2009-06-25 at 12:41 +0200, Jens Axboe wrote:
> 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.
I tested it against 2.6.31-rc1 on a couple of machines.
1) System didn't hang;
2) Comapring with previous bdi flusher versions, I didn't find clear performance
different.

>  Thanks! The target
> for this patchset is 2.6.32 and it'll be sitting (and has been for the past



      parent reply	other threads:[~2009-06-29  8:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 10:41 [PATCH 0/10] Per-bdi writeback flusher threads v12 Jens Axboe
2009-06-25 10:41 ` [PATCH 01/10] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-06-25 10:41 ` [PATCH 02/10] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-07-06 12:55   ` Artem Bityutskiy
2009-07-06 13:13     ` Jens Axboe
2009-07-06 13:26       ` Artem Bityutskiy
2009-07-07 15:27   ` Artem Bityutskiy
2009-07-08  0:57     ` Zhang, Yanmin
2009-07-08  4:47       ` Artem Bityutskiy
2009-06-25 10:41 ` [PATCH 03/10] writeback: get rid of pdflush completely Jens Axboe
2009-06-25 10:41 ` [PATCH 04/10] writeback: separate the flushing state/task from the bdi Jens Axboe
2009-06-25 10:41 ` [PATCH 05/10] writeback: support > 1 flusher thread per bdi Jens Axboe
2009-07-06 12:18   ` Artem Bityutskiy
2009-07-06 12:22     ` Jens Axboe
2009-07-06 13:37   ` Artem Bityutskiy
2009-07-06 13:49     ` Jamie Lokier
2009-07-06 14:11       ` Artem Bityutskiy
2009-07-06 15:43         ` Jens Axboe
2009-06-25 10:41 ` [PATCH 06/10] writeback: allow sleepy exit of default writeback task Jens Axboe
2009-06-25 10:42 ` [PATCH 07/10] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-06-25 10:42 ` [PATCH 08/10] writeback: add name to backing_dev_info Jens Axboe
2009-06-25 10:42 ` [PATCH 09/10] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-06-25 10:42 ` [PATCH 10/10] writeback: use spin_trylock() in bdi_writeback_all() for WB_SYNC_NONE Jens Axboe
2009-06-29  8:43 ` Zhang, Yanmin [this message]

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=1246265017.2560.446.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.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=jens.axboe@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@rsk.demon.co.uk \
    /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).