This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] dma_alloc_coherent issue with tg3 in x86_64 build

To: "Scott Parish" <srparish@xxxxxxxxxx>
Subject: RE: [Xen-devel] dma_alloc_coherent issue with tg3 in x86_64 build
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Thu, 28 Jul 2005 22:25:55 +0100
Cc: Chris Wright <chrisw@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 28 Jul 2005 21:24:25 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWTuTd25zuS9J4mQhOMk8HXuf4GQQAARjYA
Thread-topic: [Xen-devel] dma_alloc_coherent issue with tg3 in x86_64 build

> > I guess we could hold onto a few large chunks before making 
> the dom0 
> > memory allocation.
> I'm surprised that the mfns are already fragmented that early in boot.
> Or maybe this case is just an example of bad luck?

debug builds go out of their way to fragment things -- its proved useful
for catching drivers that are taking liberties. Maybe not too smart when
used in conjunction with dom0 grabbing all of memory...

It would be good to confirm that things are OK with non debug builds,
but I still don't think it's a good idea to rely on this. Let's hold a
couple of MB back from dom0 to avoid problems.


Xen-devel mailing list