> > 2. Free page tables when they're emptied, by keeping up to date
> > per-page-directory counts of used entries.
> >
> > Doesn't do anything about the overheads, but hopefully keeps them
> > bounded as a proportion of the actual page table memory used.
> >
>
> NetBSD handles this very elegantly. Because the overhead of page
> table recovery is pretty foul (especially non intel), when they need
> to reclaim memory urgently they simply blow the CPU page tables away
> and give the task a new empty page table set to page everything back
> into.
>
> Since there are caches these faults don't go to disk but just to the cache
> and rapidly recover the page tables for the current working set.
But surely with enough small segments I could overflow these caches too?
Doesn't sound like a complete solution to me.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/