public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: "jens.axboe@oracle.com" <jens.axboe@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"chris.mason@oracle.com" <chris.mason@oracle.com>
Subject: Re: [PATCH] fs: Fix busyloop in wb_writeback()
Date: Sun, 20 Sep 2009 10:35:28 +0800	[thread overview]
Message-ID: <20090920023528.GA13114@localhost> (raw)
In-Reply-To: <1253121768-20673-1-git-send-email-jack@suse.cz>

On Thu, Sep 17, 2009 at 01:22:48AM +0800, Jan Kara wrote:
> If all inodes are under writeback (e.g. in case when there's only one inode
> with dirty pages), wb_writeback() with WB_SYNC_NONE work basically degrades
> to busylooping until I_SYNC flags of the inode is cleared. Fix the problem by
> waiting on I_SYNC flags of an inode on b_more_io list in case we failed to
> write anything.

Sorry, I realized that inode_wait_for_writeback() waits for I_SYNC.
But inodes in b_more_io are not expected to have I_SYNC set. So your
patch looks like a big no-op?

The busy loop does exists, when bdi is congested.
In this case, write_cache_pages() will refuse to write anything,
we used to be calling congestion_wait() to take a breath, but now
wb_writeback() purged that call and thus created a busy loop.

So the solution (at least for this merge window)
should be to restore the congestion_wait() call.

Thanks,
Fengguang

> CC: Wu Fengguang <fengguang.wu@intel.com>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
>  fs/fs-writeback.c |   19 ++++++++++++++++++-
>  1 files changed, 18 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index 8e1e5e1..c59d673 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -706,6 +706,7 @@ static long wb_writeback(struct bdi_writeback *wb,
>  	};
>  	unsigned long oldest_jif;
>  	long wrote = 0;
> +	struct inode *inode;
>  
>  	if (wbc.for_kupdate) {
>  		wbc.older_than_this = &oldest_jif;
> @@ -747,8 +748,24 @@ static long wb_writeback(struct bdi_writeback *wb,
>  		 * If we ran out of stuff to write, bail unless more_io got set
>  		 */
>  		if (wbc.nr_to_write > 0 || wbc.pages_skipped > 0) {
> -			if (wbc.more_io && !wbc.for_kupdate)
> +			if (wbc.more_io && !wbc.for_kupdate) {
> +				if (wbc.nr_to_write < MAX_WRITEBACK_PAGES)
> +					continue;
> +				/*
> +				 * Nothing written. Wait for some inode to
> +				 * become available for writeback. Otherwise
> +				 * we'll just busyloop.
> +				 */
> +				spin_lock(&inode_lock);
> +				if (!list_empty(&wb->b_more_io))  {
> +					inode = list_entry(
> +							wb->b_more_io.prev,
> +							struct inode, i_list);
> +					inode_wait_for_writeback(inode);
> +				}
> +				spin_unlock(&inode_lock);
>  				continue;
> +			}
>  			break;
>  		}
>  	}
> -- 
> 1.6.0.2

  parent reply	other threads:[~2009-09-20  2:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 17:22 [PATCH] fs: Fix busyloop in wb_writeback() Jan Kara
2009-09-16 18:41 ` Jens Axboe
2009-09-17  9:09   ` Jan Kara
2009-09-21 13:01   ` Wu Fengguang
2009-09-21 13:06     ` Jens Axboe
2009-09-21 13:10       ` Wu Fengguang
2009-09-21 13:40         ` Jens Axboe
2009-09-21 13:19     ` Jan Kara
2009-09-21 13:28       ` Wu Fengguang
2009-09-19  1:53 ` Wu Fengguang
2009-09-20  2:35 ` Wu Fengguang [this message]
2009-09-20 17:43   ` Jan Kara
2009-09-21  1:08     ` Wu Fengguang
2009-09-21 13:45       ` Jan Kara
2009-09-21 14:11         ` Wu Fengguang
2009-09-21 14:19           ` Chris Mason
2009-09-21 14:31             ` Wu Fengguang
2009-09-21 14:45               ` Chris Mason
2009-09-22  9:14                 ` Wu Fengguang
2009-09-23  7:56 ` Wu Fengguang

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=20090920023528.GA13114@localhost \
    --to=fengguang.wu@intel.com \
    --cc=chris.mason@oracle.com \
    --cc=jack@suse.cz \
    --cc=jens.axboe@oracle.com \
    --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