public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: "Figo.zhang" <zhangtianfei@leadcoretech.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
	Wu Fengguang <fengguang.wu@intel.com>,
	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 18:10:00 +0900 (JST)	[thread overview]
Message-ID: <20101018180919.3AF8.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1287389631.1997.9.camel@myhost>

> 
> 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?

very lots of change ;)
can you please send us your crash log?




  reply	other threads:[~2010-10-18  9:10 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
2010-10-18  9:10       ` KOSAKI Motohiro [this message]
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=20101018180919.3AF8.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.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 \
    --cc=zhangtianfei@leadcoretech.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