On Fri, 25 Jan 2008 15:51:18 +0100
Andi Kleen <andi@firstfloor.org> wrote:

quoted text
> Ingo Molnar <mingo@elte.hu> writes:
> 
> > * Andi Kleen <ak@novell.com> wrote:
> >
> >> > - the new implementation is much more scalable, because it is 
> >> > lockless
> >> >   in the fastpath
> >> 
> >> What fast path?  This should not really be called that often, 
> >> especially not when DEBUG_PAGEALLOC has its own simple
> >> implementation.
> 
> > that's a point you are still missing badly in all these discussions 
> > about unification and sound design practices: code reuse and a
> > clean, layered design.
> 
> kernel_map_pages does its own thing for flushes. I must admit I always
> considered that abuse because it gives a somewhat fragile special case
> where c_p_a() is not allowed to set up any state for g_f_t() for some
> specific cases. Clean layering looks different to me.
> 
> > PAGEALLOC now uses change_page_attr() again and that 
> > approach is working really well.
> 
> I don't really see any attempt to stop the
> 
> allocation -> kernel_map_pages -> split -> allocation ->
> kernel_map_pages -> other split -> allocation -> ....
> 

but.. if you start out with everything not split, and only split on free....
well arguably that's the same thing yeah.. but it could be done such that you can use the
page you just freed for the split ;-)
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/