KOSAKI, AFAIRC, you are a person who hates android low memory killer. Why do you hate it? If it solve problems I mentioned, do you have a concern, still? If so, please, list up.
1) it took tasklist_lock. (it was solved already) 2) hacky lowmem_deathpending_timeout 3) No ZONE awareness. global_page_state(), lowmem_minfree[] and shrink_slab interface don't realize real memory footprint. 4) No memcg, cpuset awareness. 5) strange score calculation. the score is calculated from anon_rss+file_rss, but oom killer only free anon_rss. 6) strange oom_score_adj overload 7) much duplicate code w/ oom_killer. we can make common helper function, I think. 8) John's fallocate(VOLATILE) is more cleaner. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>