Re: [PATCH] i386: remove dead code in pgtable_cache_init

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Christoph Lameter <clameter@...>
Cc: Andi Kleen <ak@...>, William Lee Irwin III <wli@...>, Ingo Molnar <mingo@...>, Thomas Gleixner <tglx@...>, Andrew Morton <akpm@...>, Linux Kernel Mailing List <linux-kernel@...>
Date: Wednesday, October 10, 2007 - 5:46 pm

Christoph Lameter wrote:

Yes, Xen requires it for PAE pgds, at least at the moment.  But native,
lguest, vmi and kvm don't.  I'd made it so that the memory overhead was
only paid in the Xen case.  Allocating a whole page all the time
certainly simplifies things, but at the cost of more overhead for everyone.

If we move away from using the page->private field to link the pgds
together, then I can probably remove Xen's need to allocate a whole page
for PAE pgds.

    J
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] i386: remove dead code in pgtable_cache_init, Jeremy Fitzhardinge, (Wed Oct 10, 4:38 pm)
Re: [PATCH] i386: remove dead code in pgtable_cache_init, Christoph Lameter, (Wed Oct 10, 5:09 pm)
Re: [PATCH] i386: remove dead code in pgtable_cache_init, Jeremy Fitzhardinge, (Wed Oct 10, 5:46 pm)