From: "Figo.zhang" <zhangtianfei@leadcoretech.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rientjes@google.com" <rientjes@google.com>,
figo1802 <figo1802@gmail.com>
Subject: Re: oom_killer crash linux system
Date: Mon, 18 Oct 2010 16:13:51 +0800 [thread overview]
Message-ID: <1287389631.1997.9.camel@myhost> (raw)
In-Reply-To: <20101018021126.GB8654@localhost>
i want to test the oom-killer. My desktop (Dell optiplex 780, i686
kernel)have 2GB ram, i turn off the swap partition, and open a huge pdf
files and applications, and let the system eat huge ram.
in 2.6.35, i can use ram up to 1.75GB,
but in 2.6.36-rc8, i just use to 1.53GB ram , the system come very slow
and crashed after some minutes , the DiskIO is very busy. i see the
DiskIO read is up to 8MB/s, write just only 400KB/s, (see by conky).
what change between 2.6.35 to 2.6.36-rc8? is it low performance about
page reclaim and page writeback in high press ram useage?
Best,
Figo.zhang
On Mon, 2010-10-18 at 10:11 +0800, Wu Fengguang wrote:
> 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@leadcoretech.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@google.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
next prev parent reply other threads:[~2010-10-18 8:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 1:47 oom_killer crash linux system Figo.zhang
2010-10-18 1:57 ` KAMEZAWA Hiroyuki
2010-10-18 2:11 ` Wu Fengguang
2010-10-18 8:13 ` Figo.zhang [this message]
2010-10-18 9:10 ` KOSAKI Motohiro
2010-10-18 15:31 ` Wu Fengguang
2010-10-19 2:07 ` Figo.zhang
2010-10-19 2:59 ` KAMEZAWA Hiroyuki
2010-10-19 5:23 ` Minchan Kim
2010-10-19 5:26 ` KAMEZAWA Hiroyuki
2010-10-19 5:34 ` Minchan Kim
2010-10-20 1:35 ` Wu Fengguang
2010-10-20 2:06 ` Figo.zhang
2010-10-20 2:32 ` KOSAKI Motohiro
2010-10-20 2:58 ` Figo.zhang
2010-10-20 3:24 ` KOSAKI Motohiro
2010-10-20 3:43 ` Figo.zhang
2010-10-20 5:05 ` Adam Jiang
2010-10-19 6:22 ` KAMEZAWA Hiroyuki
2010-10-20 1:36 ` Figo.zhang
2010-10-20 1:47 ` Wu Fengguang
2010-10-19 18:43 ` David Rientjes
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=1287389631.1997.9.camel@myhost \
--to=zhangtianfei@leadcoretech.com \
--cc=fengguang.wu@intel.com \
--cc=figo1802@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox