> This patch isn't primarily a performance patch. It does help for some
> things, notably the fork/exec/exit cases mentioned above. But its primary
> goal is to reduce the amount of memory wasted in page tables mapping the
> same pages into multiple processes. We have seen an application that
> consumed on the order of 10 GB of page tables to map a single shared memory
> chunk across hundreds of processes. Shared page tables would eliminate
> this overhead.
Have you considered putting a fixed upper bound on the number of pages
tables a page can be mapped into? This would result in the same amount
of memory reduction, with what should be very little complexity.
I admit there would be a few more demand paging hits, but they should be
controllable. And I suspect their performance impact would be lost
in the noise.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/