From: David Teigland <teigland@redhat.com>
To: Shawn Guo <shawn.gsc@gmail.com>
Cc: linux-lvm@redhat.com, Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] A couple of questions on locking library
Date: Fri, 31 May 2019 09:38:26 -0500 [thread overview]
Message-ID: <20190531143826.GA25097@redhat.com> (raw)
In-Reply-To: <CAJBJ56LoBQF_cqfXwKdHVqhJfRHioBN9BJCy_fiqDRW36pCPuA@mail.gmail.com>
On Fri, May 31, 2019 at 03:13:39PM +0800, Shawn Guo wrote:
> Hi David, Zdenek,
>
> Comparing to stable-2.02 branch, I noticed that there are significant
> changes around locking infrastructure on master branch. I have a
> couple of questions regarding to these changes.
>
> 1. I see External Locking support was removed as part of clvmd
> removal. What's the reason for dropping External Locking support? I'm
> asking because we are investigating the possibility to use hardware
> assisted locking for cluster, in form of External Locking extension.
You could create other multi-host locking mechanisms in lvmlockd.
There are currently two, see lvmlockd-dlm.c and lvmlockd-sanlock.c.
Dave
prev parent reply other threads:[~2019-05-31 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 7:13 [linux-lvm] A couple of questions on locking library Shawn Guo
2019-05-31 8:38 ` Zdenek Kabelac
2019-05-31 14:47 ` Shawn Guo
2019-06-03 14:08 ` David Teigland
2019-05-31 14:38 ` David Teigland [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=20190531143826.GA25097@redhat.com \
--to=teigland@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=shawn.gsc@gmail.com \
--cc=zkabelac@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).