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 02/10] writeback: switch to per-bdi threads for flushing data
Date: Mon, 31 Aug 2009 19:29:12 +0200	[thread overview]
Message-ID: <20090831172912.GW12579@kernel.dk> (raw)
In-Reply-To: <20090831125840.GA20465@infradead.org>

On Mon, Aug 31 2009, Christoph Hellwig wrote:
> On Mon, Aug 31, 2009 at 02:14:43PM +0200, Jens Axboe wrote:
> > -static void generic_sync_bdi_inodes(struct backing_dev_info *bdi,
> > -				    struct writeback_control *wbc,
> > -				    struct super_block *sb,
> > -				    int is_blkdev_sb)
> > +void generic_sync_bdi_inodes(struct super_block *sb,
> > +			     struct writeback_control *wbc)
> 
> I think we're better off having the sb also in the writeback control.
> Now that the inodes actually hang off the backing device it's just
> another parameter to limit the amount of writeback done.

Sure no problem, I'll shove that in there.

> > +		/*
> > +		 * If this fs is currently being u/remounted, leave the
> > +		 * inode alone
> > +		 */
> > +		if (!down_read_trylock(&inode->i_sb->s_umount)) {
> > +			requeue_io(inode);
> > +			continue;
> > +		}
> 
> This looks correct to me, but I wonder if the increased traffic on
> s_umount will hurt us in some way for the writeback of lots of small
> files.

I didn't spot anything today, but I didn't have that many files in
flight (lots of cpus, though). But yes, something to keep an eye on.

> >  void generic_sync_sb_inodes(struct super_block *sb,
> >  				struct writeback_control *wbc)
> >  {
> > -	const int is_blkdev_sb = sb_is_blkdev_sb(sb);
> > -	struct backing_dev_info *bdi;
> > -
> > -	mutex_lock(&bdi_lock);
> > -	list_for_each_entry(bdi, &bdi_list, bdi_list)
> > -		generic_sync_bdi_inodes(bdi, wbc, sb, is_blkdev_sb);
> > -	mutex_unlock(&bdi_lock);
> > +	if (wbc->bdi)
> > +		generic_sync_bdi_inodes(sb, wbc);
> > +	else
> > +		bdi_writeback_all(sb, wbc);
> 
> With the sb in writeback_control this gem would also be gone.

Yeah :)

> Btw, some ordering in the patch series seems odd, e.g. you have 
> most of the high level flushing code above generic_sync_wb_inodes
> which makes reading fs-writeback.c rather inconvenient.  And also
> leads to having two forward declarations for generic_sync_wb_inodes
> beeing added inside the file.

OK, will look into cleaning that up.

-- 
Jens Axboe


  reply	other threads:[~2009-08-31 17:29 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 [this message]
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
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 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-17 11:07 [PATCH 0/10] Per-bdi writeback flusher threads v11 Jens Axboe
2009-06-17 11:07 ` [PATCH 02/10] writeback: switch to per-bdi threads for flushing data 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=20090831172912.GW12579@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).