On Sat, Dec 31, 2005 at 03:26:18PM +0100, Arjan van de Ven wrote:
> On Sat, 2005-12-31 at 17:02 +0300, Al Boldi wrote:
>
> > Shouldn't it be possible to disable overcommit completely, thus giving kswapd
> > a break from running wild trying to find something to swap/page, which is
> > the reason why the system gets unstable going over 95% in your example.
>
> shared mappings make this impractical. To disable overcommit completely,
> each process would need to account for all its own shared libraries, eg
> each process gets glibc added etc. You'll find that on any
> non-extremely-stripped system you then end up with much more memory
> needed than you have ram.
Arjan, is this true even for read-only mappings such as shared libs ?
It seems to me that those ones can precisely be mapped once because
they are areas the process cannot extend. Am I wrong ?
Willy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
