From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm: schedule during recovery loops
Date: Tue, 25 Sep 2007 11:23:11 -0500 [thread overview]
Message-ID: <20070925162311.GE15893@redhat.com> (raw)
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>
Index: linux-quilt/fs/dlm/lock.c
===================================================================
--- linux-quilt.orig/fs/dlm/lock.c
+++ linux-quilt/fs/dlm/lock.c
@@ -3997,6 +3997,7 @@ int dlm_recover_waiters_post(struct dlm_
unlock_rsb(r);
put_rsb(r);
dlm_put_lkb(lkb);
+ schedule();
}
return error;
Index: linux-quilt/fs/dlm/recover.c
===================================================================
--- linux-quilt.orig/fs/dlm/recover.c
+++ linux-quilt/fs/dlm/recover.c
@@ -533,6 +533,7 @@ int dlm_recover_locks(struct dlm_ls *ls)
}
count += r->res_recover_locks_count;
+ schedule();
}
up_read(&ls->ls_root_sem);
@@ -705,6 +706,7 @@ void dlm_recover_rsbs(struct dlm_ls *ls)
rsb_clear_flag(r, RSB_RECOVER_CONVERT);
rsb_clear_flag(r, RSB_NEW_MASTER2);
unlock_rsb(r);
+ schedule();
}
up_read(&ls->ls_root_sem);
@@ -732,6 +734,7 @@ int dlm_create_root_list(struct dlm_ls *
dlm_hold_rsb(r);
}
read_unlock(&ls->ls_rsbtbl[i].lock);
+ schedule();
}
out:
up_write(&ls->ls_root_sem);
@@ -741,11 +744,15 @@ int dlm_create_root_list(struct dlm_ls *
void dlm_release_root_list(struct dlm_ls *ls)
{
struct dlm_rsb *r, *safe;
+ unsigned int count = 0;
down_write(&ls->ls_root_sem);
list_for_each_entry_safe(r, safe, &ls->ls_root_list, res_root_list) {
list_del_init(&r->res_root_list);
dlm_put_rsb(r);
+
+ if (!(++count % 100))
+ schedule();
}
up_write(&ls->ls_root_sem);
}
@@ -763,6 +770,7 @@ void dlm_clear_toss_list(struct dlm_ls *
free_rsb(r);
}
write_unlock(&ls->ls_rsbtbl[i].lock);
+ schedule();
}
}
Index: linux-quilt/fs/dlm/requestqueue.c
===================================================================
--- linux-quilt.orig/fs/dlm/requestqueue.c
+++ linux-quilt/fs/dlm/requestqueue.c
@@ -192,6 +192,7 @@ void dlm_purge_requestqueue(struct dlm_l
list_del(&e->list);
kfree(e);
}
+ schedule();
}
mutex_unlock(&ls->ls_requestqueue_mutex);
}
next reply other threads:[~2007-09-25 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 16:23 David Teigland [this message]
2007-09-26 7:18 ` [Cluster-devel] [PATCH] dlm: schedule during recovery loops Patrick Caulfield
2007-09-26 13:25 ` David Teigland
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=20070925162311.GE15893@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).