Re: [Xen-devel] /proc/xen/xenbus supports watch?

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 26 Sep 2005, at 19:51, Christian Limpach wrote:

> > > Since we
> > > need to add some kind of transaction identifier to the interface
> > > to support this, we should make this change now.
> > Or, alternately, since we don't need it, we shouldn't.
> I think we need them since it's the simplest solution to the whole
> multi-page/multi-connection issue for a saner xenbus_dev 
> implementation:
> - lock only held around xs_talkv
> - transaction ids
> - single point for demultiplexing watch events
This is precisely how I expected that xenbus was going to be structured 
in the first place. It seems the simplest, most natural implementation 
and happens to avoid a lot of potential unnecessary blocking and 
serialisation. And not even at much cost in xenstored (how hard can the 
demultiplex be?).
 -- Keir


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