[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20091116102714.GC3328@amd.com>
Date: Mon, 16 Nov 2009 11:27:14 +0100
From: Joerg Roedel <joerg.roedel@....com>
To: Ingo Molnar <mingo@...e.hu>
CC: Pekka Enberg <penberg@...helsinki.fi>, Tejun Heo <tj@...nel.org>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
linux-kernel@...r.kernel.org, chrisw@...s-sol.org,
dwmw2@...radead.org, Andrew Morton <akpm@...ux-foundation.org>,
Yinghai Lu <yinghai@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Vegard Nossum <vegard.nossum@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Mel Gorman <mel@....ul.ie>
Subject: Re: [PATCH 07/10] bootmem: add free_bootmem_late
On Sun, Nov 08, 2009 at 10:57:19AM +0100, Ingo Molnar wrote:
> Page tables is the main dependency. x86 boots with a limited set of page
> tables, the real ones are set up later.
>
> We'd need to see what bootmem allocations are done before page table
> init in practice. I think i did such tests a few years ago and i think
> it's rather limited (if it happens at all).
>
> If that's mapped out we can just convert x86 to an 'emulated' bootmem
> allocator: buddy and slab is set up right when pagetables are set up,
> and bootmem can just use kmalloc.
That sounds like a good idea. But keep in mind that support for 1GB
pages currently depends on the bootmem allocator because the buddy
system can not allocate 1GB of physically contiguous memory.
But I think this could also be handled from x86 arch code without the
bootmem allocator.
Joerg
--
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