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
| ||
|
Message-Id: <20240905215945.1909-1-hdanton@sina.com> Date: Fri, 6 Sep 2024 05:59:45 +0800 From: Hillf Danton <hdanton@...a.com> To: Davidlohr Bueso <dave@...olabs.net> Cc: yosryahmed@...gle.com, mhocko@...nel.org, Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH -next] mm: introduce per-node proactive reclaim interface On Wed, 4 Sep 2024 09:27:40 -0700 Davidlohr Bueso <dave@...olabs.net> wrote: > This adds support for allowing proactive reclaim in general on a > NUMA system. A per-node interface extends support for beyond a > memcg-specific interface, respecting the current semantics of > memory.reclaim: respecting aging LRU and not supporting > artificially triggering eviction on nodes belonging to non-bottom > tiers. > > This patch allows userspace to do: > > echo 512M swappiness=10 > /sys/devices/system/node/nodeX/reclaim > The proactive reclaim on the cmdline looks like waste of cpu cycles before the cases where kswapd fails to work are spotted. It is not correct to add it because you can type the code.
Powered by blists - more mailing lists