linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 05/10] writeback: support > 1 flusher thread per bdi
Date: Mon, 31 Aug 2009 19:32:24 +0200	[thread overview]
Message-ID: <20090831173223.GY12579@kernel.dk> (raw)
In-Reply-To: <20090831130125.GC20465@infradead.org>

On Mon, Aug 31 2009, Christoph Hellwig wrote:
> On Mon, Aug 31, 2009 at 02:14:46PM +0200, Jens Axboe wrote:
> > Build on the bdi_writeback support by allowing registration of
> > more than 1 flusher thread. File systems can call bdi_add_flusher_task(bdi)
> > to add more flusher threads to the device. If they do so, they must also
> > provide a super_operations function to return the suitable bdi_writeback
> > struct from any given inode.
> 
> Please drop this for now.  It adds a lot of unused and untestede code
> including a dead on arrival inode operation.

OK, will drop the multi thread support, I'll retain the worker items
though.

> Once we are going to add actual multiple flusher threads we can revise
> it.  But I don't think for example that the operation in it's current
> form makese too much sense - the most logical way to add multiple
> flushers per filesystems would be having multiple bdis of some sort.

Sure, it was more of a proof-of-concept, since I think it'll be
important at higher buffered output rates with a single thread becoming
a bottle neck. But I have no issues with dropping it for now, it'll be
easy enough to re-introduce.

I'll post an updated patch series later tonight/tomorrow with the
changes.

-- 
Jens Axboe


  reply	other threads:[~2009-08-31 17:32 UTC|newest]

Thread overview: 27+ 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 [this message]
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
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 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-17 11:07 [PATCH 0/10] Per-bdi writeback flusher threads v11 Jens Axboe
2009-06-17 11:07 ` [PATCH 05/10] writeback: support > 1 flusher thread per bdi 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=20090831173223.GY12579@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).