cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 1/2] GFS2: Introduce EXSH (exclusively shared on one node)
Date: Wed, 18 Apr 2018 15:32:35 -0400 (EDT)	[thread overview]
Message-ID: <540748805.20967425.1524079955994.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <f23c53e0-eeb2-4465-92f8-ada5e935028f@redhat.com>

----- Original Message -----
> Hi,
> 
> 
> On 18/04/18 17:58, Bob Peterson wrote:
> > This patch is a first step in rgrp sharing. It allows for a new
> > type of glock mode called EXSH, which stands for a lock that is
> > Exclusive to one node, but shared amongst processes on that node.
> > Like a Shared glock, multiple processes may acquire the lock in
> > EXSH mode at the same time, provided they're all on the same
> > node. All other nodes will see this as an EX lock. In other words,
> > to the DLM, the lock is granted to the node in EX, but at the
> > glock layer, they may be shared.
> >
> > For now, there are no users of the new EXSH glock mode.
> > Future patches will use it to improve performance with rgrp sharing.
> Is there a reason why we cannot just add a lock flag here, rather than
> requiring a new lock state? That should make it a much smaller change,
> and leaves the lock state always reflecting the cluster lock state,
> 
> Steve.

Hi,

Well, yes, we can add a new lock flag. The new locking mode just
gave me more clarity how I thought about things. A flag ought to
work just as well.

I was also trying to extrapolate how we can use this in the future
for other types of local lock sharing, but we can also do that
with the same flag.

Also, I had originally coded it so it did everything through glops,
but I decided it was just too confusing to follow.

Regards,

Bob Peterson
Red Hat File Systems



  reply	other threads:[~2018-04-18 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 16:58 [Cluster-devel] [GFS2 PATCH v1 0/2] Improve throughput through rgrp sharing Bob Peterson
2018-04-18 16:58 ` [Cluster-devel] [GFS2 PATCH 1/2] GFS2: Introduce EXSH (exclusively shared on one node) Bob Peterson
2018-04-18 19:13   ` Steven Whitehouse
2018-04-18 19:32     ` Bob Peterson [this message]
2018-04-19  8:29       ` Steven Whitehouse
2018-04-18 16:58 ` [Cluster-devel] [GFS2 PATCH 2/2] GFS2: Take advantage of new EXSH glock mode for rgrps Bob Peterson
2018-04-18 19:25   ` Steven Whitehouse
2018-04-18 19:39     ` Bob Peterson
2018-04-19  8:43       ` Steven Whitehouse

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=540748805.20967425.1524079955994.JavaMail.zimbra@redhat.com \
    --to=rpeterso@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).