[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Locking block devices for concurrent access?
From: |
Richard W.M. Jones |
Subject: |
Re: [Qemu-devel] Locking block devices for concurrent access? |
Date: |
Thu, 22 Apr 2010 20:21:09 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
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: <address@hidden>
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