linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <zhiyuan_zhu@htc.com>
To: vinmenon@codeaurora.org
Cc: linux-mm@kvack.org
Subject: Low memory killer problem
Date: Mon, 15 May 2017 03:58:15 +0000	[thread overview]
Message-ID: <AF7C0ADF1FEABA4DABABB97411952A2EDD0A4E5E@CN-MBX03.HTC.COM.TW> (raw)
In-Reply-To: <AF7C0ADF1FEABA4DABABB97411952A2EDD0A004D@CN-MBX05.HTC.COM.TW>

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

Loop Linux-mm, thanks.
I want to know, why lowmemory killer not included ION free memory?
Thnanks.


From: Zhiyuan Zhu(朱志遠)
Sent: Friday, May 12, 2017 4:56 PM
To: vinmenon@codeaurora.org
Cc: Kyle Lin(林昭凱); Zhiyuan Zhu(朱志遠)
Subject: Low memory killer problem

Dear Vinmenon,

I found a part of ION memory will be return to system in android platform,
But these memorys  can’t accounted in low-memory-killer strategy.
…
And I also found ION memory comes from, kmalloc/vmalloc/alloc pages/reserved memory.
What affect if account these memorys for free?
Many thanks.

…
Lowmemory killer strategy
af6c02b83 (Vinayak Menon      2015-08-27 16:29:37 +0530 418)            global_page_state(NR_FILE_PAGES) + zcache_pages())
af6c02b83 (Vinayak Menon      2015-08-27 16:29:37 +0530 419)            other_file = global_page_state(NR_FILE_PAGES) + zcache_pages() -
058dbde92 (Vinayak Menon      2014-02-27 00:36:22 +0530 420)                                            global_page_state(NR_SHMEM) -
058dbde92 (Vinayak Menon      2014-02-27 00:36:22 +0530 422)                                            total_swapcache_pages();



Meminfo example
$ adb shell cat /proc/meminfo
MemTotal:        3805312 kB
MemFree:         1446220 kB
MemAvailable:    2388384 kB
Buffers:           16796 kB
Cached:          1190868 kB
…
IonTotal:         224252 kB
IonInUse:         199108 kB



Thanks
BR
Zhiyuan zhu

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

       reply	other threads:[~2017-05-15  3:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AF7C0ADF1FEABA4DABABB97411952A2EDD0A004D@CN-MBX05.HTC.COM.TW>
2017-05-15  3:58 ` zhiyuan_zhu [this message]
2017-05-15  7:25 ` zhiyuan_zhu
2017-05-15  8:05   ` Greg KH
2017-05-15  8:22     ` zhiyuan_zhu
2017-05-15  9:00       ` Greg KH
2017-05-16  3:41         ` zhiyuan_zhu
2017-05-16  5:56           ` Greg KH
2017-05-16 22:37           ` Laura Abbott
2017-05-17  2:47             ` zhiyuan_zhu

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=AF7C0ADF1FEABA4DABABB97411952A2EDD0A4E5E@CN-MBX03.HTC.COM.TW \
    --to=zhiyuan_zhu@htc.com \
    --cc=linux-mm@kvack.org \
    --cc=vinmenon@codeaurora.org \
    /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