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

[Bill Davidsen]

On Tue, 22 Oct 2002, Martin J. Bligh wrote:

> > 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 ?

That tradeoff makes the case for spt being a kbuild or /proc/sys option. A
linear speedup of fork/exec/exit is likely to be more generally useful,
most people just don't have huge shared areas. On the other hand, those
who do would get a vast improvement, and that would put Linux a major step
forward in the server competition.
 
> 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 ;-)

I'm just trying to decide what this might do for a news server with
hundreds of readers mmap()ing a GB history file. Benchmarks show the 2.5
has more latency the 2.4, and this is likely to make that more obvious.

Is there any way to to have this only on processes which really need it?
define that any way you wish, including hanging a capability on the
executable to get spt.

-- 
bill davidsen <[e-mail]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.