From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] dlm: don't require FS flag on all nodes
Date: Mon, 11 Jun 2007 16:51:31 +0100 [thread overview]
Message-ID: <1181577091.25918.303.camel@quoit> (raw)
In-Reply-To: <20070611154718.GA19371@redhat.com>
Hi,
Now pushed to the GFS2 -nmw git tree. Thanks,
Steve.
On Mon, 2007-06-11 at 10:47 -0500, David Teigland wrote:
> Mask off the recently added DLM_LSFL_FS flag when setting the exflags.
> This way all the nodes in the lockspace aren't required to have the FS
> flag set, since we later check that exflags matches among all nodes.
>
> Signed-off-by: Patrick Caulfield <pcaulfie@redhat.com>
> Signed-off-by: David Teigland <teigland@redhat.com>
>
> Index: linux-quilt/fs/dlm/lockspace.c
> ===================================================================
> --- linux-quilt.orig/fs/dlm/lockspace.c 2007-06-06 08:47:45.000000000 -0500
> +++ linux-quilt/fs/dlm/lockspace.c 2007-06-11 10:34:28.000000000 -0500
> @@ -438,17 +438,18 @@
> ls->ls_count = 0;
> ls->ls_flags = 0;
>
> - /* ls_exflags are forced to match among nodes, and we don't
> - need to require all nodes to have TIMEWARN active */
> if (flags & DLM_LSFL_TIMEWARN)
> set_bit(LSFL_TIMEWARN, &ls->ls_flags);
> - ls->ls_exflags = (flags & ~DLM_LSFL_TIMEWARN);
>
> if (flags & DLM_LSFL_FS)
> ls->ls_allocation = GFP_NOFS;
> else
> ls->ls_allocation = GFP_KERNEL;
>
> + /* ls_exflags are forced to match among nodes, and we don't
> + need to require all nodes to have TIMEWARN or FS set */
> + ls->ls_exflags = (flags & ~(DLM_LSFL_TIMEWARN | DLM_LSFL_FS));
> +
> size = dlm_config.ci_rsbtbl_size;
> ls->ls_rsbtbl_size = size;
>
prev parent reply other threads:[~2007-06-11 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 15:47 [Cluster-devel] [PATCH] dlm: don't require FS flag on all nodes David Teigland
2007-06-11 15:51 ` Steven Whitehouse [this message]
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=1181577091.25918.303.camel@quoit \
--to=swhiteho@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.