--2k0lXb7fQrut5C7L
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 10, 2006 at 12:00:56AM +0100, Manuel Bouyer wrote:
> > Is it something that can be influenced by the ELF headers of the dom0
> > kernel?  I know there were some changes recently (as part of the 3.0.3
> > support) to load addresses and other possibly promising parameters..
>=20
> Actually putting a limit on dom0 memory may not be enough; a network buff=
er
> from a domU can end up in the DMA descriptor of the network adapter

Hm, I suppose so.  Normally this would be a good thing. :-)

Would it matter if the traffic was being bridged vs routed? Probably not.

> > Any other clues?
>=20
> How does the driver deal with this limitation ? Does it work with a plain
> i386 kernel ?

It doesn't.  There have been some unsucessful attempts at a bounce-buffer
style solution in the driver, and some discussion of adding various kinds
of more general "dma constraints" properties, but at present the driver
just fails if used with >1G native.  Both of these ideas would probably get
even more complicated under Xen.

--
Dan.
--2k0lXb7fQrut5C7L
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)

iD8DBQFFU7d+EAVxvV4N66cRAqrWAJ9Ui/0Q0yLtoxlDX8fmjgFyC7TyHwCg50kO
PMvD9hxQ79nCs94HHqpsK2A=
=wzjb
-----END PGP SIGNATURE-----

--2k0lXb7fQrut5C7L--