linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <zhiyuan_zhu@htc.com>
To: hannes@cmpxchg.org
Cc: Future_Zhou@htc.com, Rachel_Zhang@htc.com, mhocko@suse.cz,
	bsingharora@gmail.com, kamezawa.hiroyu@jp.fujitsu.com,
	cgroups@vger.kernel.org, linux-mm@kvack.org,
	majordomo@vger.kernel.org
Subject: low memory killer
Date: Thu, 20 Nov 2014 09:26:05 +0000	[thread overview]
Message-ID: <AF7C0ADF1FEABA4DABABB97411952A2EC91E38@CN-MBX02.HTC.COM.TW> (raw)

[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]

hi Johannes

My name is Zhiyuan zhu, an android development engineer in htc.
We encounter a lowmemorykiller’s problem.
Coluld you help to kindly support? Thank you.

Problem describtion:
We noticed that gap of dumping cached value from “lowmemorykiller” and “/proc/meminfo/” are different apparently. Like example below, lowmemorykiller showed cache only has 72460kB while launcher was killed, but /proc/meminfo showed cached still has 142448kB. Please check why the gap of cache value between lowmemorykill and /proc/meminfo are huge.

kernel_e0058_0001_20141107_204711_LC4ABYA00200_htc_a31ul_0.54.999.1.txt at LC4ABYA00200
        6      161030.084144       2014-11-07 21:44:53.304        lowmemorykiller: Killing 'om.htc.launcher' (4486), adj 294,
6      161030.084144       2014-11-07 21:44:53.304           to free 47856kB on behalf of 'kworker/u8:14' (20594) because
6      161030.084144       2014-11-07 21:44:53.304           cache 72460kB is below limit 73728kB for oom_score_adj 235
6      161030.084144       2014-11-07 21:44:53.304           Free memory is 51304kB above reserved
4      161030.084797       2014-11-07 21:44:53.304        MemFree:           55676 kB
4      161030.084797       2014-11-07 21:44:53.304        Buffers:            1240 kB
4      161030.084797       2014-11-07 21:44:53.304        Cached:           142448 kB

Lowmemorykiller calculated cache value is 72460kB, but the /proc/meminfo’s cached is 142448 kB

After checked the code, I found that:
Lowmemorykiller’s memory information is comes from /proc/zoneinfo file’s nr_file_pages
So I want to know how different the /proc/zoneinfo file’s nr_file_pages and /proc/meminfo file’s Cached ?

Thanks
Zhiyuan zhu

MEMORY RESOURCE CONTROLLER
M: Johannes Weiner <hannes@cmpxchg.org>
M: Michal Hocko <mhocko@suse.cz>
M: Balbir Singh <bsingharora@gmail.com>
M: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
L:   cgroups@vger.kernel.org
L:   linux-mm@kvack.org
S:  Maintained
F:  mm/memcontrol.c
F:  mm/page_cgroup.c

[-- Attachment #2: Type: text/html, Size: 34203 bytes --]

             reply	other threads:[~2014-11-20  9:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  9:26 zhiyuan_zhu [this message]
2014-11-20  9:58 ` Michal Hocko
2014-11-20 10:09   ` 答复: " zhiyuan_zhu
2014-11-20 10:18     ` Michal Hocko
2014-11-20 12:05       ` 答复: " zhiyuan_zhu
2014-11-20 14:19         ` Weijie Yang
2014-11-24 16:17         ` Michal Hocko

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=AF7C0ADF1FEABA4DABABB97411952A2EC91E38@CN-MBX02.HTC.COM.TW \
    --to=zhiyuan_zhu@htc.com \
    --cc=Future_Zhou@htc.com \
    --cc=Rachel_Zhang@htc.com \
    --cc=bsingharora@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=majordomo@vger.kernel.org \
    --cc=mhocko@suse.cz \
    /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