[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Transactions and watches

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Jacob Gorm Hansen <jacobg@xxxxxxx>
  • Date: Wed, 5 Oct 2005 18:44:02 +0200
  • Delivery-date: Wed, 05 Oct 2005 16:41:34 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=F3XGwHWTgUV5i5YZxqhuQX+p86wRlJnoQWbT80JmuKe/wkAKLmYD6UppdDLdGUG6cb7etqMA3XeAYt81jNZwNloFbud80g1Uka61adGR0TnsQDPSmNwRGvaWqtGKOvj2x12zjGdfYyQ9rICg5X/GJfzEwM0CIc3CIoTbsRLUyKg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


in my experimentation with xenbus, it seems that I get markedly
different results when using straigth xs_write's rather than nesting
them inside transactions. I suppose that the idea is that the watches
get triggered on transaction_end, but even if I enclose each xs_write
in it's own transaction I get different results.

Are transactions working the way they are supposed to, or is my
understanding wrong?


Save time and bandwidth with EDelta: http://www.diku.dk/~jacobg/edelta/

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.