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 lockqueue.c
Date: Mon, 23 Jan 2006 21:58:00 -0000	[thread overview]
Message-ID: <20060123215845.29756.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	STABLE
Changes by:	teigland@sourceware.org	2006-01-23 21:58:45

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

Log message:
	When GFS uses direct-io PR and CW locks are mixed together
	on a single resource.  To optimize the interaction between
	these two lock modes, GFS uses LM_FLAG_ANY to request that
	either of the modes be granted.  When the dlm carries out
	this optimization and grants a PR lock instead of a CW, or
	a CW instead of a PR, the mode is not switched on the non-
	master node.  So, for example, the lock will be requested
	in PR mode with the ALTCW flag, it will be granted on the
	master node in CW mode, but the non master (requesting)
	node will record the granted mode as PR.
	
	Fix by changing the grmode on the non-master node when we
	get ALTMODE back from the master.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/dlm-kernel/src/lockqueue.c.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.37.2.6.6.4&r2=1.37.2.6.6.5


             reply	other threads:[~2006-01-23 21:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 21:58 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-14 15:57 teigland
2008-01-04 16:12 teigland
2007-11-07 15:57 teigland
2007-11-07 15:22 teigland
2006-01-24 17:46 teigland
2006-01-24 17:16 teigland
2006-01-24 14:38 teigland
2005-12-19 23:01 teigland
2005-12-19 22:55 teigland
2005-12-16 20:18 teigland
2005-12-16 16:39 teigland
2005-12-14 23:24 teigland
2005-12-14 23:20 teigland
2005-02-17  4:38 teigland
2005-02-17  4:37 teigland
2005-02-16  3:53 teigland
2005-02-16  3:52 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=20060123215845.29756.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).