Re: [PATCH 2.5.43-mm2] New shared page table patch

[Martin J. Bligh]

> Actually, per-object reverse mappings are nowhere near as good
> a solution as shared page tables.  At least, not from the points
> of view of space consumption and the overhead of tearing down
> the mappings at pageout time.
> 
> Per-object reverse mappings are better for fork+exec+exit speed,
> though.
> 
> It's a tradeoff: do we care more for a linear speedup of fork(),
> exec() and exit() than we care about a possibly exponential
> slowdown of the pageout code ?

As long as the box doesn't fall flat on it's face in a jibbering
heap, that's the first order of priority ... ie I don't care much
for now ;-)

M.