From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [RFC PATCH v3 2/2] xfs: fix xfsaild hang due to lost wake ups
Date: Thu, 24 May 2012 10:06:26 +1000 [thread overview]
Message-ID: <20120524000626.GP25351@dastard> (raw)
In-Reply-To: <4FBD2306.8090000@redhat.com>
On Wed, May 23, 2012 at 01:48:54PM -0400, Brian Foster wrote:
> On 05/22/2012 08:58 PM, Dave Chinner wrote: snip
> >
> > Finally, rather than calling wake_up_process() in the
> > xfs_ail_push*() functions, call wake_up(&ailp->xa_idle); There
> > can only be one thread sleeping on that (the xfsaild) so there
> > is no need to use the wake_up_all() variant...
> >
> > FWIW, you might be able to do this without the idle wait queue
> > and just use wake_up_process() -
> >
>
> Hi Dave,
>
> I have a working version of your suggested algorithm. It looks
> mostly the same with the exception of a spin_unlock fix. I also
> have the below version that uses a wait_queue and that I plan to
> test overnight tonight:
See my previous mail about using an idle queue.
> while (!kthread_should_stop()) {
> if (tout && tout <= 20)
> state = TASK_KILLABLE;
> else
> state = TASK_INTERRUPTIBLE;
>
> prepare_to_wait(&ailp->xa_idle, &wait, state);
>
> spin_lock(&ailp->xa_lock);
> /* barrier matches the xa_target update in xfs_ail_push() */
> smp_rmb();
> if (!xfs_ail_min(ailp) && (ailp->xa_target == ailp->xa_target_prev)) {
> /* the ail is empty and no change to the push target - idle */
> spin_unlock(&ailp->xa_lock);
> schedule();
> } else if (tout) {
> spin_unlock(&ailp->xa_lock);
> /* more work to do soon */
> schedule_timeout(msecs_to_jiffies(tout));
> } else {
> spin_unlock(&ailp->xa_lock);
> }
Three separate unlocks? that's a recipe for future disasters. how
about:
if (!xfs_ail_min(ailp) && (ailp->xa_target == ailp->xa_target_prev)) {
/* the ail is empty and no change to the push target - idle */
spin_unlock(&ailp->xa_lock);
schedule();
tout = 0;
continue;
}
spin_unlock(&ailp->xa_lock);
if (tout) {
/* more work to do soon */
schedule_timeout(msecs_to_jiffies(tout));
}
So that we recheck the idle condition on wakeup from idle before
doing anything. (i.e. handle spurious idle wakeups effectively). By
setting the tout to zero, we then fall through immediately to
pushing the AIL if it was a real wakeup that moved the target....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-24 0:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 16:38 [RFC PATCH v3 0/2] xfs: fix xfsaild races and re-enable idle mode Brian Foster
2012-05-22 16:38 ` [RFC PATCH v3 1/2] xfs: re-enable xfsaild idle mode when the ail is empty Brian Foster
2012-05-22 16:38 ` [RFC PATCH v3 2/2] xfs: fix xfsaild hang due to lost wake ups Brian Foster
2012-05-23 0:58 ` Dave Chinner
2012-05-23 13:05 ` Brian Foster
2012-05-24 0:01 ` Dave Chinner
2012-05-23 17:48 ` Brian Foster
2012-05-23 18:19 ` Mark Tinguely
2012-05-23 23:41 ` Brian Foster
2012-05-23 23:53 ` Dave Chinner
2012-05-24 14:38 ` Mark Tinguely
2012-05-24 0:06 ` Dave Chinner [this message]
2012-05-24 13:07 ` Brian Foster
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=20120524000626.GP25351@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.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