[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49BEAA61.4020208@goop.org>
Date: Mon, 16 Mar 2009 12:37:05 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Jan Beulich <jbeulich@...ell.com>
CC: "H. Peter Anvin" <hpa@...or.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
the arch/x86 maintainers <x86@...nel.org>,
David Airlie <airlied@...ux.ie>,
Xen-devel <xen-devel@...ts.xensource.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH 10/27] xen: make sure swiotlb allocation
isphysically contigious
Jan Beulich wrote:
>
> While on native using alloc_bootmem_low_pages() is a requirement here,
> on Xen this should explicitly not be used, as we realized just a couple of
> days ago:
Which conversation was this?
> The way the bootmem allocator works, running out of space
> below 4Gb is pretty easy on machines with lots of memory, and since the
> swiotlb is a requirement for Dom0, the risk of allocation failures must be
> kept as low as possible.
>
Are we talking about a 32 or 64 bit dom0 here? If its 32-bit, then yes,
low memory is a precious resource, but I don't see why that depends on
the total amount of memory. And if its 64-bit, why is below-4G
particularly constrained? That would only matter for 32-bit devices?
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists