Re: fast path for anonymous memory allocation

[Christoph Lameter <clameter@sgi.com>]

On Fri, 19 Nov 2004, Nick Piggin wrote:

> But you're doing it after you've set up a pte for that page you are
> clearing... I think? What's to stop another thread trying to read or
> write to it concurrently?

Nothing. If this had led to anything then we would have needed to address
this issue. The clearing had to be outside of the lock in order not to
impact the performance tests negatively.

> > If you do the clearing with the page table lock held then performance will
> > suffer.
> Yeah very much, but if you allocate and clear a "just in case" page
> _before_ taking any locks for the fault then you'd be able to go
> straight through do_anonymous_page.
>
> But yeah that has other issues like having a spare page per CPU (maybe
> not so great a loss), and having anonymous faults much more likely to
> get pages which are cache cold.

You may be able to implement that using the hot and cold lists. Have
something that runs on the lists and prezeros and preformats these pages
(idle thread?).

Set some flag to indicate that a page has been prepared and then just zing
it in if do_anymous_page finds that flag said.

But I think this may be introduce way too much complexity
into the page fault handler.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>