Attached (sorry, couldn't get it to not word-wrap inline) is a patch to remove 
incorrect documentation regarding overcommit.

On Tuesday 09 August 2005 11:06, you wrote:
> vinay wrote:
> > I have a problem with linux kernel's Out Of Memory (OOM) killer.

You're not alone.

> This condition should not occur without using overcommit. Are you sure
> you are not using overcommit ? (cat /proc/sys/vm/overcommit_memory)
>
> To dasable it:
> echo 0 > /proc/sys/vm/overcommit_memory

The documentation seems forked on this point, and from what I can see from the 
source (mm/mmap.c and include/linux/mman.h) 
Documentation/filesystems/proc.txt is wrong and Documentation/sysctl/vm.txt 
is right.

#define OVERCOMMIT_NEVER		2

> Overcommit is quite dangerous on production systems, because it leads to
> oom kills on heavy loads (at least, this is what I experienced).

... and it's on by default. bleh.



---------
typedef struct me_s {
  char name[]      = { "Thomas Habets" };
  char email[]     = { "thomas@habets.pp.se" };
  char kernel[]    = { "Linux" };
  char *pgpKey[]   = { "http://www.habets.pp.se/pubkey.txt" };
  char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE  0945 286A E90A AD48 E854" };
  char coolcmd[]   = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;