lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 20 Feb 2020 17:27:28 -0800 From: Mike Kravetz <mike.kravetz@...cle.com> To: Joel Savitz <jsavitz@...hat.com>, linux-kernel@...r.kernel.org Cc: Andrew Morton <akpm@...ux-foundation.org>, Rafael Aquini <aquini@...hat.com>, linux-mm@...ck.org Subject: Re: [PATCH] mm/page_alloc: increase default min_free_kbytes bound On 2/20/20 7:01 AM, Joel Savitz wrote: > > Further work to make the calculation of vm.min_free_kbytes more > consistent throughout the kernel would be desirable. > > As an example of the inconsistency of the current method, this value is > recalculated by init_per_zone_wmark_min() in the case of memory hotplug > which will override the value set by set_recommended_min_free_kbytes() > called during khugepaged initialization even if khugepaged remains > enabled, however an on/off toggle of khugepaged will then recalculate > and set the value via set_recommended_min_free_kbytes(). I took a shot at fixing some of those inconsistencies. https://lore.kernel.org/linux-mm/20200210190121.10670-1-mike.kravetz@oracle.com/ -- Mike Kravetz
Powered by blists - more mailing lists