From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
chris.mason@oracle.com, david@fromorbit.com,
akpm@linux-foundation.org, jack@suse.cz
Subject: Re: [PATCH 06/10] writeback: allow sleepy exit of default writeback task
Date: Mon, 31 Aug 2009 19:32:40 +0200 [thread overview]
Message-ID: <20090831173240.GZ12579@kernel.dk> (raw)
In-Reply-To: <20090831130230.GD20465@infradead.org>
On Mon, Aug 31 2009, Christoph Hellwig wrote:
> On Mon, Aug 31, 2009 at 02:14:47PM +0200, Jens Axboe wrote:
> > Since we do lazy create of default writeback tasks for a bdi, we can
> > allow sleepy exit if it has been completely idle for 5 minutes.
>
> Any reason this is not merged into patch 2?
Separate functional change, but could easily be merged in #2.
--
Jens Axboe
next prev parent reply other threads:[~2009-08-31 17:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 12:14 [PATCH 0/10] Per-bdi writeback flusher threads v14 Jens Axboe
2009-08-31 12:14 ` [PATCH 01/10] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-08-31 12:14 ` [PATCH 02/10] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-08-31 12:58 ` Christoph Hellwig
2009-08-31 17:29 ` Jens Axboe
2009-08-31 12:14 ` [PATCH 03/10] writeback: get rid of pdflush completely Jens Axboe
2009-08-31 12:59 ` Christoph Hellwig
2009-08-31 17:29 ` Jens Axboe
2009-08-31 12:14 ` [PATCH 04/10] writeback: separate the flushing state/task from the bdi Jens Axboe
2009-08-31 12:14 ` [PATCH 05/10] writeback: support > 1 flusher thread per bdi Jens Axboe
2009-08-31 13:01 ` Christoph Hellwig
2009-08-31 17:32 ` Jens Axboe
2009-08-31 12:14 ` [PATCH 06/10] writeback: allow sleepy exit of default writeback task Jens Axboe
2009-08-31 13:02 ` Christoph Hellwig
2009-08-31 17:32 ` Jens Axboe [this message]
2009-08-31 12:14 ` [PATCH 07/10] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-08-31 12:14 ` [PATCH 08/10] writeback: add name to backing_dev_info Jens Axboe
2009-08-31 12:14 ` [PATCH 09/10] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-08-31 12:14 ` [PATCH 10/10] vm: Add an tuning knob for vm.max_writeback_pages Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2009-06-25 10:41 [PATCH 0/10] Per-bdi writeback flusher threads v12 Jens Axboe
2009-06-25 10:41 ` [PATCH 06/10] writeback: allow sleepy exit of default writeback task Jens Axboe
2009-06-17 11:07 [PATCH 0/10] Per-bdi writeback flusher threads v11 Jens Axboe
2009-06-17 11:07 ` [PATCH 06/10] writeback: allow sleepy exit of default writeback task 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=20090831173240.GZ12579@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).