From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm: schedule during recovery loops
Date: Wed, 26 Sep 2007 08:25:11 -0500 [thread overview]
Message-ID: <20070926132511.GB15033@redhat.com> (raw)
In-Reply-To: <46FA07DF.6040902@redhat.com>
On Wed, Sep 26, 2007 at 08:18:55AM +0100, Patrick Caulfield wrote:
> David Teigland wrote:
> > Call schedule() in a bunch of places where the recovery code loops
> > through lists of locks. The theory is that these lists become so
> > long that looping through them triggers the softlockup watchdog.
> > (usually on ia64, doesn't seem to happen often on other arch's).
> >
> > Signed-off-by: David Teigland <teigland@redhat.com>
>
>
> I think we're encouraged to use cond_resched() instead these days. It has the
> same effect but doesn't force a schedule if there is nothing else to run.
OK, I'd like to try to do cond_resched() instead, how certain are we that
it's just as effective in avoiding the softlockup watchdog? Testing it is
going to be difficult since it's largely unreproducable outside of some
single cpu ia64 machines in the qe dept...
next prev parent reply other threads:[~2007-09-26 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 16:23 [Cluster-devel] [PATCH] dlm: schedule during recovery loops David Teigland
2007-09-26 7:18 ` Patrick Caulfield
2007-09-26 13:25 ` David Teigland [this message]
2007-09-26 13:52 ` Patrick Caulfield
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=20070926132511.GB15033@redhat.com \
--to=teigland@redhat.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;
as well as URLs for NNTP newsgroup(s).