[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101018021126.GB8654@localhost>
Date: Mon, 18 Oct 2010 10:11:26 +0800
From: Wu Fengguang <fengguang.wu@...el.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: "Figo.zhang" <zhangtianfei@...dcoretech.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"rientjes@...gle.com" <rientjes@...gle.com>,
figo1802 <figo1802@...il.com>
Subject: Re: oom_killer crash linux system
On Mon, Oct 18, 2010 at 09:57:22AM +0800, KAMEZAWA Hiroyuki wrote:
> On Mon, 18 Oct 2010 09:47:39 +0800
> "Figo.zhang" <zhangtianfei@...dcoretech.com> wrote:
>
> > hi all,
> >
> > i have a desktop run linux2.6.35 and have 2GB ram. i turn off the swap
> > partition, and i open huge applications , let the system eat more and
> > more memory.
> > when the system eat more than 1.7G ram, the system crashed.
> >
>
> 2.6.36-rc series has a completely new logic, please try.
And the new logic should help this case.
commit a63d83f427fbce97a6cea0db2e64b0eb8435cd10
Author: David Rientjes <rientjes@...gle.com>
Date: Mon Aug 9 17:19:46 2010 -0700
oom: badness heuristic rewrite
...
Instead of basing the heuristic on mm->total_vm for each task, the task's
rss and swap space is used instead. This is a better indication of the
amount of memory that will be freeable if the oom killed task is chosen
and subsequently exits. This helps specifically in cases where KDE or
GNOME is chosen for oom kill on desktop systems instead of a memory
hogging task.
...
Thanks,
Fengguang
--
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