xen-devel

[Top] [All Lists]

[Xen-devel] Transaction mapping in xenstored

from [John Levon]

[Permanent Link][Original]

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-devel] Transaction mapping in xenstored
From:	John Levon <levon@xxxxxxxxxxxxxxxxx>
Date:	Tue, 6 Mar 2007 11:24:42 +0000
Delivery-date:	Tue, 06 Mar 2007 03:20:42 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mutt/1.5.9i

(Sorry, lost Keir's mail).

I'm unclear on why we have to have the mapping part of solving the
xendev problem. Can't we just allocate a transaction as usual if we see
an ID without a transaction existing, mark it as pre-fail, and when we
see the transaction end, discard the copy as if it had raced?

Surely the ID lookup is guaranteed to fail in the circumstances we care
about (restore, xenstored restart)?

regards
john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] Transaction mapping in xenstored, John Levon <= Re: [Xen-devel] Transaction mapping in xenstored, Keir Fraser

Previous by Date:	Re: [Xen-devel] GNU Mach Xen port, Mark Williamson
Next by Date:	Re: [Xen-devel] COW in Xen, Mark Ryden
Previous by Thread:	[Xen-devel] xm block-list fails, Jan Agermose
Next by Thread:	Re: [Xen-devel] Transaction mapping in xenstored, Keir Fraser
Indexes:	[Date] [Thread] [Top] [All Lists]