| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
On Thu, 2006-02-16 at 16:06 -0800, Magenheimer, Dan (HP Labs Fort
Collins) wrote:
> I count this as the third recent attempt to add an abstraction
> layer for interdomain page mapping/communication/transport.
> (YAIDTL = yet another interdomain transport layer)
Yes. I think there's a consensus that the current code is patchy, to
say the least. It's an open question how drastic the surgury needs to
be.
For my part, I'm not in a particular hurry: I'm aiming for xen 4.0, and
there's lots of work to be done between here and there. Incremental
improvements to the existing code will no doubt continue in shorter
timeframes.
My issue with Xen continues to be that it is too complex, hence my
attempts to implement a minimal efficient interface. We will see what
it looks like once it's feature-complete, portable, etc.
> Surely this is relevant to the core Xen developers? And
> surely when it is time to push the Xen drivers upstream,
> the Linux driver community reviewers will notice the issue?
I'm fairly sure kernel people will gag on the current xenbus and driver
code, yes. They might not consider it their problem, however, since
they don't have to support it.
Rusty.
--
ccontrol: http://ozlabs.org/~rusty/ccontrol
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home