All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lakshmi Narasimhan Sundararajan <lns@portworx.com>
To: lvm-devel@redhat.com
Subject: Reg concurrent access through lvmapp api
Date: Mon, 12 Aug 2019 10:12:02 +0530	[thread overview]
Message-ID: <5d50ee1b.1c69fb81.fdf43.ce3c@mx.google.com> (raw)
In-Reply-To: <5d4d1831.1c69fb81.38595.d627@mx.google.com>

Gentle reminder? I would sincerely appreciate clarification on the below.

Regards
LN
Sent from Mail for Windows 10

From: Lakshmi Narasimhan Sundararajan
Sent: Friday, August 9, 2019 12:22 PM
To: lvm-devel@redhat.com
Subject: Reg concurrent access through lvmapp api

Hi Team,
Is concurrent access to operations on lvm through lvm2app api possible?
I expected lvm2app api call to be self aware of multiple operations and lock access internal, but I see some crash while doing device creation/deletion and query in parallel.

So my question is, are basic crud (create/read/update and delete) operations on a vg safe to be operated concurrently through the lvm2app api calls? 
If not, what kind of restrictions does the end app needs to know while using lvm2app api calls?

I also understand that the cli uses a /run/lvm/lvm.lock file to control concurrent access. So does it imply that applications have to enforce serialization? If yes, what are the cases for which this needs to be enforced.

Seeking some clarity on the same.

Regards
LN
Sent from Mail for Windows 10


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20190812/4c1df0fb/attachment.htm>

           reply	other threads:[~2019-08-12  4:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5d4d1831.1c69fb81.38595.d627@mx.google.com>]

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=5d50ee1b.1c69fb81.fdf43.ce3c@mx.google.com \
    --to=lns@portworx.com \
    --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.