| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] xenbus message id's
James Harper writes ("RE: [Xen-devel] xenbus message id's"):
> I agree. I will now proceed to stupefy my implementation to make it a
> bit easier to work with :)
I agree with Keir that this is fine. The implications are just for
performance but that's probably not important in your application. If
that turns out not to be true then souping up your implementation can
be done later.
docs/misc/xenstore.txt has this to say on this subject:
A caller who sends several requests may receive the replies in any
order and must use req_id (and tx_id, if applicable) to match up
replies to requests. (The current implementation always replies to
requests in the order received but this should not be relied on.)
Here a `caller' is a counterparty communicating with xenstored via the
interdomain page/event channel mechanism or locally in dom0 via a
socket - ie your driver.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home