Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262777AbTKYRPc (ORCPT ); Tue, 25 Nov 2003 12:15:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262782AbTKYRPc (ORCPT ); Tue, 25 Nov 2003 12:15:32 -0500 Received: from mail4-141.ewetel.de ([212.6.122.141]:58611 "EHLO mail4.ewetel.de") by vger.kernel.org with ESMTP id S262777AbTKYRPZ (ORCPT ); Tue, 25 Nov 2003 12:15:25 -0500 To: "Ihar 'Philips' Filipau" Cc: linux-kernel@vger.kernel.org Subject: Re: Linux 2.4.23-rc5 In-Reply-To: References: Date: Tue, 25 Nov 2003 18:15:21 +0100 Message-Id: From: Pascal Schmidt X-CheckCompat: OK Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 843 Lines: 26 On Tue, 25 Nov 2003 17:50:20 +0100, you wrote in linux.kernel: > "overcommit_memory < 0" supposed to not allow apps to overallocate > memory - but still it works not like it is said in > Documentation/filesystems/proc.txt. Actually, looking at vm_enough_memory in mm/mmap.c in 2.4, which seems to be the only user of sysctl_overcommit_memory, it is just used directly in an if clause: if (sysctl_overcommit_memory) return 1; This means any value different from 0 will turn overcommit on, no matter whether positive or negative value. Documentation bug, I would say. -- Ciao, Pascal - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/