[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100130125917.600beb51@lxorguk.ukuu.org.uk>
Date: Sat, 30 Jan 2010 12:59:17 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: vedran.furac@...il.com
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>, rientjes@...gle.com,
minchan.kim@...il.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com>
Subject: Re: [PATCH v3] oom-kill: add lowmem usage aware oom kill handling
> > So how about you go and have a complain at the people who are causing
> > your problem, rather than the kernel.
>
> That would pass completely unnoticed and ignored as long as overcommit
> is enabled by default.
Defaults are set by the distributions. So you are still complaining to
the wrong people.
> So, if you don't want to change the OOM algorithm why not fixing this
> bug then? And after that change the proc(5) manpage entry for
> /proc/sys/vm/overcommit_memory into something like:
>
> 0: heuristic overcommit (enable this if you have memory problems with
> some buggy software)
> 1: always overcommit, never check
> 2: always check, never overcommit (this is the default)
Because there are a lot of systems where heuristic overcommit makes
sense ?
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists