Re: Memory overcommitting (was Re: http://www.redhat.com/redhat/)

Systemkennung Linux (linux@mailhost.uni-koblenz.de)
Sat, 22 Feb 1997 19:33:56 +0100 (MET)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: =?ISO-8859-1?Q?Tom=E1s_Restrepo?=: "sockaddr_in structure in in.h"
Previous message: Guilhem Lavaux: "Re: Behavior of feof()"
In reply to: Leigh Koven: "pgcc libc & cyrix 6x86"

> >One thing that is missing in Linux is the possibility to *disable* the
> >overcommitment, which is very usefull for some applications...
>
> Agreed. I also agree that we should at least have the option
> to disable overcommitment for those people who feel that they need it.

I'd like to see this as a per process option. Should this option
be inherited across fork/clone/exec?

Ralf

Next message: =?ISO-8859-1?Q?Tom=E1s_Restrepo?=: "sockaddr_in structure in in.h"
Previous message: Guilhem Lavaux: "Re: Behavior of feof()"
In reply to: Leigh Koven: "pgcc libc & cyrix 6x86"