|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] xenbus message id's
Looking through the xenbus code in the linux kernel, it seems that only
one outstanding request is allowed at a time (via a mutex), so there is
no code that uses the 'id' field in any way.
Under mini-os though, it seems like we can have a number of requests on
the fly at the same time (more complex code). This is the code I based
gplpv on.
Can anyone comment on why that is so? I'm trying to implement the xenbus
kernel<->userspace interface and was wondering why the id of the request
is accepted verbatim from userspace, but I guess if only one outstanding
request at a time is allowed then it's not a problem.
Unless there is a good reason to allow multiple outstanding requests,
I'll change the xenbus code in GPLPV to be more like the linux version
as it looks quite a bit simpler. xenbus is hardly a performance
sensitive interface...
Thanks
James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] xenbus message id's,
James Harper <=
|
|
|
|
|