From: Adam Jiang <jiang.adam@gmail.com>
To: "Figo.zhang" <zhangtianfei@leadcoretech.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Wu Fengguang <fengguang.wu@intel.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rientjes@google.com" <rientjes@google.com>,
figo1802 <figo1802@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: oom_killer crash linux system
Date: Wed, 20 Oct 2010 14:05:18 +0900 [thread overview]
Message-ID: <20101020050518.GD5796@rcwf64-moto> (raw)
In-Reply-To: <1287546225.2121.14.camel@myhost>
On Wed, Oct 20, 2010 at 11:43:45AM +0800, Figo.zhang wrote:
>
> > > active_anon:398375 inactive_anon:82967 isolated_anon:0
> > > active_file:81 inactive_file:429 isolated_file:32
> > > unevictable:13 dirty:2 writeback:14 unstable:0
> > > free:11942 slab_reclaimable:2391 slab_unreclaimable:3303
> > > mapped:5617 shmem:33909 pagetables:2280 bounce:0
> >
> > active_anon + inactive_anon + isolated_anon = 481342 pages ~= 1.8GB
> > Um, this oom doesn't makes accounting lost.
> >
> > > total 515071 2011
> >
> > page-types show similar result.
> >
> >
> > The big difference is, previous and current are showing some different processes.
> > only previous has VirtualBox, only current has vmware-usbarbit, etc..
> >
> > Can you use same test environment?
> yes, it is the same desktop, and i open some pdf files and applications
> by random.
>
> but when my desktop eat up to 1.8GB RAM (active_anon + inactive_anon +
> isolated_anon = 481342 pages >= 1.8GB), the system became extraordinary
> slow. when i move the mouse, the mouse cant move a little on screen. i
> deem it have "crashed", but i ping it's ip by other desktop, it is ok.
>
> so what is apect affect the system seem to "crashed", page-writeback?
> page-reclaimed? and the oom-killer seem to be very conservative? in
> that condition , oom_killer must kill some process to release memory for
> new process.
I think it just simply the test caused system *almost* dead but not
really trigger oom-killer. You have 2GB RAM, right. 0.2G is a huge
amount of memory for Linux kernel.
If you do want to test the new oom-killer, you can just right a simple
program to allocate memory continues but make different instances to
eat memory in different paces. Then, you can find out who will be killed
first eventually.
/Adam
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: Adam Jiang <jiang.adam@gmail.com>
To: "Figo.zhang" <zhangtianfei@leadcoretech.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Wu Fengguang <fengguang.wu@intel.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rientjes@google.com" <rientjes@google.com>,
figo1802 <figo1802@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: oom_killer crash linux system
Date: Wed, 20 Oct 2010 14:05:18 +0900 [thread overview]
Message-ID: <20101020050518.GD5796@rcwf64-moto> (raw)
In-Reply-To: <1287546225.2121.14.camel@myhost>
On Wed, Oct 20, 2010 at 11:43:45AM +0800, Figo.zhang wrote:
>
> > > active_anon:398375 inactive_anon:82967 isolated_anon:0
> > > active_file:81 inactive_file:429 isolated_file:32
> > > unevictable:13 dirty:2 writeback:14 unstable:0
> > > free:11942 slab_reclaimable:2391 slab_unreclaimable:3303
> > > mapped:5617 shmem:33909 pagetables:2280 bounce:0
> >
> > active_anon + inactive_anon + isolated_anon = 481342 pages ~= 1.8GB
> > Um, this oom doesn't makes accounting lost.
> >
> > > total 515071 2011
> >
> > page-types show similar result.
> >
> >
> > The big difference is, previous and current are showing some different processes.
> > only previous has VirtualBox, only current has vmware-usbarbit, etc..
> >
> > Can you use same test environment?
> yes, it is the same desktop, and i open some pdf files and applications
> by random.
>
> but when my desktop eat up to 1.8GB RAM (active_anon + inactive_anon +
> isolated_anon = 481342 pages >= 1.8GB), the system became extraordinary
> slow. when i move the mouse, the mouse cant move a little on screen. i
> deem it have "crashed", but i ping it's ip by other desktop, it is ok.
>
> so what is apect affect the system seem to "crashed", page-writeback?
> page-reclaimed? and the oom-killer seem to be very conservative? in
> that condition , oom_killer must kill some process to release memory for
> new process.
I think it just simply the test caused system *almost* dead but not
really trigger oom-killer. You have 2GB RAM, right. 0.2G is a huge
amount of memory for Linux kernel.
If you do want to test the new oom-killer, you can just right a simple
program to allocate memory continues but make different instances to
eat memory in different paces. Then, you can find out who will be killed
first eventually.
/Adam
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-10-20 5:05 UTC|newest]
Thread overview: 33+ 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
2010-10-18 15:31 ` Wu Fengguang
2010-10-19 2:07 ` Figo.zhang
2010-10-19 2:59 ` KAMEZAWA Hiroyuki
2010-10-19 2:59 ` KAMEZAWA Hiroyuki
2010-10-19 5:23 ` Minchan Kim
2010-10-19 5:23 ` Minchan Kim
2010-10-19 5:26 ` KAMEZAWA Hiroyuki
2010-10-19 5:26 ` KAMEZAWA Hiroyuki
2010-10-19 5:34 ` Minchan Kim
2010-10-19 5:34 ` Minchan Kim
2010-10-20 1:35 ` Wu Fengguang
2010-10-20 1:35 ` Wu Fengguang
2010-10-20 2:06 ` Figo.zhang
2010-10-20 2:06 ` Figo.zhang
2010-10-20 2:32 ` KOSAKI Motohiro
2010-10-20 2:32 ` KOSAKI Motohiro
2010-10-20 2:58 ` Figo.zhang
2010-10-20 2:58 ` Figo.zhang
2010-10-20 3:24 ` KOSAKI Motohiro
2010-10-20 3:24 ` KOSAKI Motohiro
2010-10-20 3:43 ` Figo.zhang
2010-10-20 3:43 ` Figo.zhang
2010-10-20 5:05 ` Adam Jiang [this message]
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=20101020050518.GD5796@rcwf64-moto \
--to=jiang.adam@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=figo1802@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--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 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.