Re: [PATCH] overcommit symbolic constants

From: Hugh Dickins
Date: Thu Sep 30 2004 - 09:29:18 EST


On Thu, 30 Sep 2004 Andries.Brouwer@xxxxxx wrote:
> Played a bit with overcommit the past hour.
> Am not entirely satisfied with the no overcommit mode 2 -
> programs segfault when the system is close to that boundary.
> So, instead of the somewhat larger patch that I planned to send,
> just symbolic names for the modes.

Big improvement. And thank you for stamping on that irritating
oxymoronic "strict overcommit". Could we add this patch in too?

Signed-off-by: Hugh Dickins <hugh@xxxxxxxxxxx>

--- 2.6.9-rc3/Documentation/sysctl/vm.txt 2004-08-14 06:39:04.000000000 +0100
+++ linux/Documentation/sysctl/vm.txt 2004-09-30 15:23:22.340731368 +0100
@@ -47,7 +47,7 @@ of free memory left when userspace reque
When this flag is 1, the kernel pretends there is always enough
memory until it actually runs out.

-When this flag is 2, the kernel uses a "strict overcommit"
+When this flag is 2, the kernel uses a "never overcommit"
policy that attempts to prevent any overcommit of memory.

This feature can be very useful because there are a lot of

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/