From: "Richard W.M. Jones" <rjones@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Locking block devices for concurrent access?
Date: Thu, 22 Apr 2010 20:21:09 +0100 [thread overview]
Message-ID: <20100422192109.GI5858@amd.home.annexia.org> (raw)
In-Reply-To: <4BD0972E.9080709@codemonkey.ws>
On Thu, Apr 22, 2010 at 01:36:30PM -0500, Anthony Liguori wrote:
> I think we got to the point where there was general agreement on the
> usefulness of lock=read|write but where there was still some contention
> was on this whole notion of lock=exclusive|shared.
>
> I believe Richard Jones was driving the original patch and his use case
> was libguestfs which really wants lock=exclusive (sort of). But IMHO,
> it's very confusing compared to lock=read|write.
>From the libguestfs point of view, any sort of locking would be
preferable to the current situation. If someone wants to run with the
patch, I posted several versions and there was a lot of discussion on
qemu-devel in Nov/Dec 2009, starting with this message:
Subject: [Qemu-devel] [PATCH] Disk image shared and exclusive locks.
Message-ID: <20091204165301.GA4167@amd.home.annexia.org>
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
programs, test, and build Windows installers. Over 70 libraries supprt'd
http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw
next prev parent reply other threads:[~2010-04-22 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 19:49 [Qemu-devel] Locking block devices for concurrent access? Michael Tokarev
2010-04-22 10:09 ` Michael Tokarev
2010-04-22 18:36 ` Anthony Liguori
2010-04-22 19:21 ` Richard W.M. Jones [this message]
2010-04-22 19:57 ` Michael Tokarev
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=20100422192109.GI5858@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/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).