On Fri, 06 Sep 2024, Hillf Danton wrote:\n
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.
Are you against proactive reclaim altogether (ie: memcg) or this patch in particular, which extends its availability? The benefits of proactive reclaim are well documented, and the community has been overall favorable towards it. This operation is not meant to be generally used, but there are real latency benefits to be had which are completely unrelated to watermarks. Similarly, we have 'compact' as an alternative to kcompactd (which was once upon a time part of kswapd).
