[lkml]   [2002]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2.5.43-mm2] New shared page table patch
On Mon, 21 Oct 2002, Martin J. Bligh wrote:

> > I will agree with that if everything works so the sharing happens,
> > this is a nice feature.
> I think it will for most of the situations we run aground with now
> (normally 5000 oracle tasks sharing a 2Gb shared segment, or some
> such monster).

10 GB pagetable overhead, for 2 GB of data. No customer I
know would accept that much OS overhead.

To reduce the overhead we could either reclaim the page
tables and reconstruct them when needed (lots of work) or
we could share the page tables (less runtime overhead).

> >> The ultimate solution is per-object reverse mappings, rather than per
> >> page, but that's a 2.7 thingy now.
> > ???
> >
> > Last I checked we already had those in 2.4.x, and still in 2.5.x. The
> > list of place the address space is mapped.
> It's more complicated than that ... I'll let Rik or one of the K42
> guys who understand it better than I do explain it (yeah, I'm
> wimping out on you ;-))

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,

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 ?

(note that William Irwin and myself have a trick to turn the
possible exponential slowdown of the pageout code into something
better ... just a few details left)


A: No.
Q: Should I include quotations after my reply?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:30    [W:0.123 / U:3.428 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site