public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] Prevent excessive xfsaild wakeups
Date: Wed, 20 Feb 2008 08:12:00 -0600	[thread overview]
Message-ID: <47BC3530.1080803@sandeen.net> (raw)
In-Reply-To: <20080220055318.GO155407@sgi.com>

David Chinner wrote:
> ping?
> 
> This is needed for 2.6.25-rcX....
> 
> On Tue, Feb 19, 2008 at 09:59:06AM +1100, David Chinner wrote:
>> Idle state is not being detected properly by the xfsaild push
>> code. The current idle state is detected by an empty list
>> which may never happen with mostly idle filesystem or one
>> using lazy superblock counters. A single dirty item in the
>> list will result repeated looping to push everything past
>> the target when everything because it fails to check if we
>> managed to push anything.
>>
>> Fix by considering a dirty list with everything past the target
>> as an idle state and set the timeout appropriately.

Seems good to me.

Acked-by: Eric Sandeen <sandeen@sandeen.net>

-Eric

>> Signed-off-by: Dave Chinner <dgc@sgi.com>
>> ---
>>  fs/xfs/xfs_trans_ail.c |   15 +++++++++------
>>  1 file changed, 9 insertions(+), 6 deletions(-)
>>
>> Index: 2.6.x-xfs-new/fs/xfs/xfs_trans_ail.c
>> ===================================================================
>> --- 2.6.x-xfs-new.orig/fs/xfs/xfs_trans_ail.c	2008-02-18 09:14:34.000000000 +1100
>> +++ 2.6.x-xfs-new/fs/xfs/xfs_trans_ail.c	2008-02-18 09:18:52.070682570 +1100
>> @@ -261,14 +261,17 @@ xfsaild_push(
>>  		xfs_log_force(mp, (xfs_lsn_t)0, XFS_LOG_FORCE);
>>  	}
>>  
>> -	/*
>> -	 * We reached the target so wait a bit longer for I/O to complete and
>> -	 * remove pushed items from the AIL before we start the next scan from
>> -	 * the start of the AIL.
>> -	 */
>> -	if ((XFS_LSN_CMP(lsn, target) >= 0)) {
>> +	if (count && (XFS_LSN_CMP(lsn, target) >= 0)) {
>> +		/*
>> +		 * We reached the target so wait a bit longer for I/O to
>> +		 * complete and remove pushed items from the AIL before we
>> +		 * start the next scan from the start of the AIL.
>> +		 */
>>  		tout += 20;
>>  		last_pushed_lsn = 0;
>> +	} else if (!count) {
>> +		/* We're past our target or empty, so idle */
>> +		tout = 1000;
>>  	} else if ((restarts > XFS_TRANS_PUSH_AIL_RESTARTS) ||
>>  		   (count && ((stuck * 100) / count > 90))) {
>>  		/*
> 

  reply	other threads:[~2008-02-20 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 22:59 [patch] Prevent excessive xfsaild wakeups David Chinner
2008-02-20  5:53 ` David Chinner
2008-02-20 14:12   ` Eric Sandeen [this message]
2008-02-20 19:10 ` Christoph Hellwig
2008-02-21 22:47   ` David Chinner

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=47BC3530.1080803@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=dgc@sgi.com \
    --cc=xfs-dev@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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