Thanks Laura, Indeed, some part of ION memory have registered shrinker. /proc/meminfo have no account for the memory which ION can be shrinked part, but just have IonTotal and IonInUse. And another problem is: ION memory is special, maybe hard to reclaim. So, wating for Google's solution now. By the way, which E-mail client do you use? :) Thanks Zhiyuan zhu -----Original Message----- From: Laura Abbott [mailto:labbott@xxxxxxxxxx] Sent: Wednesday, May 17, 2017 6:37 AM To: Zhiyuan Zhu(朱志遠); gregkh@xxxxxxxxxxxxxxxxxxx Cc: vinmenon@xxxxxxxxxxxxxx; linux-mm@xxxxxxxxx; skhiani@xxxxxxxxxxxxxx; torvalds@xxxxxxxxxxxxxxxxxxxx; Jet Li(李發傑) Subject: Re: Low memory killer problem On 05/15/2017 08:41 PM, zhiyuan_zhu@xxxxxxx wrote: > Thanks for your remind, > I found lowmemorykiller.c have been removed, and ION module still exist since v4.12-rc1. > I will pay attention to ION module. > > But I still have 3 questions, > Is there any substitute for low-memory-killer after kernel v4.12-rc1 ? > Can I accounted the ION free to free memory? > Is there any different from ION free and the normal system memory free? > > ION free means: IonTotal - IonInUse - ION reserved memory. > Thanks a lot. > Issues like this are exactly why the LMK was deleted. The problem is the LMK is hooked up as a shrinker so it runs in parallel to any other shrinker. The short answer is yes if you want the LMK to do anything reasonable you probably need to tweak it to account for other memory that may be held in the system (Ion, zswap etc.). There never seemed to be one universal heuristic that worked for everyone which was part of the reason why most changes exist downstream. Using some combination of the Ion variables above would work if you experiment. If this sounds like a non-answer, that's because it is. Thanks, Laura > -----Original Message----- > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Monday, May 15, 2017 5:00 PM > To: Zhiyuan Zhu(朱志遠) > Cc: vinmenon@xxxxxxxxxxxxxx; linux-mm@xxxxxxxxx; > skhiani@xxxxxxxxxxxxxx; torvalds@xxxxxxxxxxxxxxxxxxxx; Jet Li(李發傑) > Subject: Re: Low memory killer problem > > On Mon, May 15, 2017 at 08:22:38AM +0000, zhiyuan_zhu@xxxxxxx wrote: >> Dear Greg, >> >> Very sorry my mail history is lost. >> >> 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. >> I understand reserved memory shouldn't accounted to free memory. >> But the memory which alloced by kmalloc/vmalloc/alloc pages, can be reclaimed. >> >> But the low-memory killer can't accounted this part, Many thanks. >> >> Code location, >> ---> drivers/staging/android/lowmemorykiller.c -> lowmem_scan > > That file is gone from the latest kernel release, sorry. So there's not much we can do about this code anymore. > > See the mailing list archives for what should be used instead of this code, there is a plan for what to do. > > Also note that the ION code has had a lot of reworks lately as well. > > good luck! > > greg k-h > > N r zǧu Ơ{ 칻 &ޖ) i ^n r ݢj$ $ ~ '.) ,y m > % { j+ צj)Z f {d $ /a== > ��.n������g��� �a��� �&ޖ)���)��h���&������梷���� �Ǟ�m������)������^�����������v���O��zf������
