From: Avi Kivity <avi@argo.co.il>
To: Coywolf Qi Hunt <qiyong@fc-cn.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] make sysctl_overcommit_memory enumeration sensible
Date: Wed, 15 Feb 2006 12:32:38 +0200 [thread overview]
Message-ID: <43F30346.1070802@argo.co.il> (raw)
In-Reply-To: <20060215093136.GA2600@localhost.localdomain>
Coywolf Qi Hunt wrote:
>On Wed, Feb 15, 2006 at 01:05:59AM -0800, Andrew Morton wrote:
>
>
>>Coywolf Qi Hunt <qiyong@fc-cn.com> wrote:
>>
>>
>>>I see system admins often confused when they sysctl vm.overcommit_memory.
>>>This patch makes overcommit_memory enumeration sensible.
>>>
>>>0 - no overcommit
>>>1 - always overcommit
>>>2 - heuristic overcommit (default)
>>>
>>>I don't feel this would break any userspace scripts.
>>>
>>>
>>eh? If any such scripts exist, they'll break.
>>
>>Confused.
>>
>>
>
>That's a corner case. Let'em break and fix. Otherwise, users will
>be confused. Even they get it right, after some weeks they'll have
>to re-read the doc. A logical user interface is important to human.
>
>
If I have
vm.overcommit_memory = 2
in my /etc/sysctl.conf, its meaning silently changes. I'll know about it
during the next oomkiller pass.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2006-02-15 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 8:54 [patch] make sysctl_overcommit_memory enumeration sensible Coywolf Qi Hunt
2006-02-15 9:01 ` Nick Piggin
2006-02-15 13:50 ` Mark Hahn
2006-02-16 1:28 ` Coywolf Qi Hunt
2006-02-16 5:05 ` Nick Piggin
2006-02-15 9:05 ` Andrew Morton
2006-02-15 9:31 ` Coywolf Qi Hunt
2006-02-15 10:32 ` Avi Kivity [this message]
2006-02-15 10:43 ` Coywolf Qi Hunt
2006-02-15 13:04 ` Avi Kivity
2006-02-16 1:29 ` Coywolf Qi Hunt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F30346.1070802@argo.co.il \
--to=avi@argo.co.il \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiyong@fc-cn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.