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


[Xen-devel] xs transaction

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] xs transaction
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 11 Sep 2007 15:17:55 +0800
Delivery-date: Tue, 11 Sep 2007 00:18:32 -0700
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
Thread-index: Acf0Q9+kPHP1cHSpSZSDVBFVO42XRA==
Thread-topic: xs transaction
Seems currently xenstore transaction provides confusing message 
in different places:

a) comment of xs_transaction_start says "You can only have one 
transaction at any time." However do_transaction_start allows up to 
10 transactions created, as long as all other existing transaction 
channel is idle at the time (conn->transaction == NULL)

b) when multiple transactions can be created, xenstore is not ready 
to handle traffic in parallel. Only one conn->transaction exists 

c) do_transaction_start says "/* We don't support nested transactions. 
*/" by checking conn->transaction, but it can't handle nest case. 
Conn->transaction only indicates whether traffic is on-going in other 
transaction, instead of whether other transactions are created. Instead 
conn->transaction_list should be checked for the purpose.

So what's expected usage for current xs transaction? Should xenstore 
add check on parallel/nest case, or depend on caller to avoid?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>