> That added to the fact that last time someone ran the numbers linux> was considerably faster than the BSD for mm type operations when not> swapping. And this is the common case.

"Linux VM works wonderfully when nobody is using it"

Which is rather like the scheduler works well for one task then by three ismaking bad decisions.

> But I have not seen the argument that not having reverse maps make it> undoable. In fact previous versions of linux seem to put the proof> that you can get at least reasonable swapping under load without> reverse page tables.

The last decent Linx VM behaviour was about 2.1.100 or so - which waswithout reverse maps. It's been downhill since then. So yes you may beright.

> So my suggestion was to look at getting anonymous pages backed by what> amounts to a shared memory segment. In that vein. By using an extent> based data structure we can get the cost down under the current 8 bits> per page that we have for the swap counts, and make allocating swap> pages faster. And we want to cluster related swap pages anyway so> an extent based system is a natural fit.

Much of this goes away if you get rid of both the swap and anonymous pagespecial cases. Back anonymous pages with the "whoops everything I write herevanishes mysteriously" file system and swap with a swapfs

Reverse mappings make linear aging easier to do but are not critical (wecan walk all physical pages via the page map array).