All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.gsc@gmail.com>
To: David Teigland <teigland@redhat.com>,
	Zdenek Kabelac <zkabelac@redhat.com>
Cc: linux-lvm@redhat.com
Subject: [linux-lvm] A couple of questions on locking library
Date: Fri, 31 May 2019 15:13:39 +0800	[thread overview]
Message-ID: <CAJBJ56LoBQF_cqfXwKdHVqhJfRHioBN9BJCy_fiqDRW36pCPuA@mail.gmail.com> (raw)

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.

2. It seems there have never been real support for LV (Logic Volume)
locking.  On stable-2.02 branch, the LV locking interface is used as
activation path instead of real locking on LV.  And on master branch,
activation path gets separated off from locking infrastructure.  As
the result, the LV interface is dropped completely from locking
infrastructure.  My question is why there have never been LV locking
support.  Is the LV locking support an invalid requirement at all?  Or
it's just because no one cares about it enough to add the support?

Thanks for your time, and appreciate any comment you would give here.

Regards,
Shawn

             reply	other threads:[~2019-05-31  7:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31  7:13 Shawn Guo [this message]
2019-05-31  8:38 ` [linux-lvm] A couple of questions on locking library Zdenek Kabelac
2019-05-31 14:47   ` Shawn Guo
2019-06-03 14:08     ` David Teigland
2019-05-31 14:38 ` David 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=CAJBJ56LoBQF_cqfXwKdHVqhJfRHioBN9BJCy_fiqDRW36pCPuA@mail.gmail.com \
    --to=shawn.gsc@gmail.com \
    --cc=linux-lvm@redhat.com \
    --cc=teigland@redhat.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 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.