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>,
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 11:32:38 +0900 (JST) [thread overview]
Message-ID: <20101020112828.1818.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1287540415.2069.1.camel@myhost>
>
> > > page_add_file_rmap() just counts an event where mapcount goes 0->1.
> > > Even if thousands process shares a page, it's just counted into file_mapped as 1.
> > >
> > > Then, there are 480MB of mapped file caches. Do I miss something ?
> > >
> > > Anyway, sum-of-all-lru-of-highmem is 480MB smaller than present pages.
> > > and isolated(anon/file) is 0kB.
> > > (NORMAL has similar problem)
> >
> > hugetlb files? But it's a desktop box. Figo, what's your meminfo?
> >
> > The GEM objects may be files not in LRU, however they should be
> > accounted into shmem.
> >
> > Figo, would you run "page-types -r" for some clues? It can be compiled
> > from the kernel tree:
> >
> > cd linux
> > make Documentation/vm
> > sudo Documentation/vm/page-types -r
>
> hi fengguang,
> here is the "page-types -r" result:
>
> flags page-count MB symbolic-flags
> long-symbolic-flags
> 0x0000000000005828 74342 290 ___U_l_____Ma_b___________________ uptodate,lru,mmap,anonymous,swapbacked
> 0x0000000000005868 373077 1457 ___U_lA____Ma_b___________________ uptodate,lru,active,mmap,anonymous,swapbacked
1457+290=1747MB. that's ok. and this is very different result with your
previous oom log.
can you please try 1) invoke oom 2) get page-types -r again. I'm curious
that oom makes page accounting lost again. I mean, please send us oom
log and "page-types -r" result.
thanks.
--
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 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101018021126.GB8654@localhost>
[not found] ` <1287389631.1997.9.camel@myhost>
[not found] ` <20101018180919.3AF8.A69D9226@jp.fujitsu.com>
[not found] ` <1287454058.2078.12.camel@myhost>
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 [this message]
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
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=20101020112828.1818.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox