All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: lvm-devel@redhat.com
Subject: [LVM2 RFCv1 4/5] lib: locking: Parse PV list for IDM locking
Date: Thu, 29 Apr 2021 11:36:10 +0800	[thread overview]
Message-ID: <20210429033610.GC199698@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20210429031209.GA199698@leoy-ThinkPad-X240s>

On Thu, Apr 29, 2021 at 11:12:09AM +0800, Leo Yan wrote:

[...]

> > > +	/*
> > > +	 * Create the VG's PV list when start the VG, the PV list
> > > +	 * is passed to lvmlockd, and the the PVs path will be used
> > > +	 * to send SCSI commands for idm locking scheme.
> > > +	 */
> > 
> > if vg->lock_type is IDM before creating pv_list?
> 
> Yes, IIUC, when start the VG, "vg->lock_type" has been assigned to the
> locking scheme which it's using; for IDM locking scheme, "vg->lock_type"
> is "idm" before creating pv_list.

No sure if I understand your question or not.  But I think you are
suggesting to check "vg->lock_type" is IDM and then create pv_list for
IDM type.  Will refine code for this.

Thanks,
Leo



  reply	other threads:[~2021-04-29  3:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  2:22 [LVM2 RFCv1 0/5] Enable In-Drive-Mutex Locking scheme Leo Yan
2021-04-25  2:22 ` [LVM2 RFCv1 1/5] lvmlockd: idm: Introduce new locking scheme Leo Yan
2021-04-28 19:54   ` David Teigland
2021-04-29  3:26     ` Leo Yan
2021-04-29 15:31       ` David Teigland
2021-04-25  2:22 ` [LVM2 RFCv1 2/5] lvmlockd: idm: Hook Seagate IDM wrapper APIs Leo Yan
2021-04-25  2:22 ` [LVM2 RFCv1 3/5] lib: locking: Add new type "idm" Leo Yan
2021-04-25  2:22 ` [LVM2 RFCv1 4/5] lib: locking: Parse PV list for IDM locking Leo Yan
2021-04-28 19:39   ` David Teigland
2021-04-29  3:12     ` Leo Yan
2021-04-29  3:36       ` Leo Yan [this message]
2021-04-25  2:22 ` [LVM2 RFCv1 5/5] tools: Add support for "idm" lock type Leo Yan
2021-04-27 22:23 ` [LVM2 RFCv1 0/5] Enable In-Drive-Mutex Locking scheme David Teigland
2021-04-28  1:50   ` Leo Yan

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=20210429033610.GC199698@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=lvm-devel@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.