Re: Fw: [Xen-devel] Xen on /. again

["Mark A. Williamson" <mark.williamson@xxxxxxxxxxxx>]

> > You might want to have two domU's shared memory to implement a "direct
> > point-to-point" ethernet link, to avoid the overheads of going through
> > dom0. For most people this might not matter but it's nice to have the
> > option for maximal performance.
>
> This should be possible by using the xen front & backend network drivers,
> right? The only thing right now is that i can't see how to get the backend
> interface to be created anywhere other than dom0.

Currently the backend driver will only start if it's in dom0 or in a network 
backend domain.  The main obstacles to doing this are:
1) the backend domain currently needs to be privileged in order to map the 
frontends memory, so this can't work between an arbitrary pair of domUs (this 
is beginning to change as grant tables are integrated).
2) the tools don't support this kind of configuration yet

> NB2: Again, i don't know if it's still the case, but the network backend
> driver can't be built without physical device access enabled, but there
> isn't a dependency for that in the kernel config system.

Since the current assumption is that the backend controls a physical 
interface, the backend is built iff the domain has physical device support.  
Might need to change in future...

Cheers,
Mark


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel