Loop MM maintainers, Dear All, Who can talk about this problem? Thanks. Maybe this is lowmemory killer’s bug ? ION memory is complex now, we need to have a breakdown for them, I think. Thanks a lot Zhiyuan zhu From: Zhiyuan Zhu(朱志遠) Sent: Friday, May 12, 2017 4:56 PM To: vinmenon@xxxxxxxxxxxxxx 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) - 5c4698e38 (kyle_lin 2015-04-16 16:04:22 +0800 421) global_page_state(NR_MLOCK) - 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
