public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: teigland@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/dlm-kernel/src locking.c
Date: Wed, 23 Feb 2005 07:37:00 -0000	[thread overview]
Message-ID: <20050223073738.11184.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland@sourceware.org	2005-02-23 07:37:38

Modified files:
	dlm-kernel/src : locking.c 

Log message:
	When locks on the convert queue are granted, we need to try again to grant
	locks from the beginning of the convert queue.  Locks at the beginning may
	not be grantable because of locks at the end.  But, granting locks at the
	end (permitted when using the NOORDER flag) may make earlier locks
	grantable.  Specifically, we have the following situation when running
	"gfs_tool freeze" in parallel on three machines:
	
	Granted 1 PR
	2 PR
	3 PR
	
	* nodeid 3 converts PR->CW
	
	Granted 1 PR
	2 PR
	Convert 3 PR->CW
	
	* nodeid 2 converts PR->CW
	granted mode is demoted to avoid conversion deadlock
	
	Granted 1 PR
	Convert 2 NL->CW
	3 PR->CW
	
	* nodeid 1 converts PR->CW
	granted mode is demoted to avoid conversion deadlock
	
	Granted
	Convert 1 NL->CW
	2 NL->CW
	3 PR->CW
	
	* conversions for 1 and 2 are blocked by 3's PR
	* conversion for 3 is granted
	
	Granted 3 CW
	Convert 1 NL->CW
	2 NL->CW
	
	* other conversions are now grantable, we must try to grant them again

Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/dlm-kernel/src/locking.c.diff?cvsroot=cluster&r1=1.56&r2=1.57


             reply	other threads:[~2005-02-23  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23  7:37 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-14 17:14 teigland
2006-07-07 15:24 teigland
2006-06-22 14:29 teigland
2005-02-23  7:39 teigland
2005-02-22  6:51 teigland
2005-02-22  6:50 teigland

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=20050223073738.11184.qmail@sourceware.org \
    --to=teigland@sourceware.org \
    --cc=cluster-cvs@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).