This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-tools] [BUNDLE] Change transaction semantics, implementation

To: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-tools] [BUNDLE] Change transaction semantics, implementation
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 21 Sep 2005 10:46:02 +0100
Cc: Xen Tools <xen-tools@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 21 Sep 2005 09:38:43 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1127282835.14188.42.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-tools-request@lists.xensource.com?subject=help>
List-id: Xen control tools developers <xen-tools.lists.xensource.com>
List-post: <mailto:xen-tools@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=unsubscribe>
References: <1127282835.14188.42.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-tools-bounces@xxxxxxxxxxxxxxxxxxx

On 21 Sep 2005, at 07:07, Rusty Russell wrote:

Previously we used a
lock to implement transactions, with deadlock protection by breaking the lock after one second and returning ETIMEDOUT. Unfortunately, the store
was so slow that we were seeing this (and treating it as a soft error,
which makes it worse, risking livelock), and Christian pointed out that
this model is also flawed in theory: domains can be paused for infinite
duration. So, transaction_end can now fail with EAGAIN at any time: you
have to loop.

This makes me very happy. :-)

 -- Keir

Xen-tools mailing list