Hey, On 7/6/26 21:25, Tejun Heo wrote: > Hello, > > On Fri, Jul 03, 2026 at 03:05:38PM +0200, Thomas Hellström wrote: >> Also honor O_NONBLOCK so that if that flag is set during the >> max value write, no reclaim is initiated. The idea is to avoid >> charging the reclaim cost to the writer of the max value. > > Is this really necessary? I'm not necessarily against it but this is trivial > to work around from userspace and feels like a gratuitous addition. What's > the use case?
The usecase is similar to the usecase in memcg's max/high, it allows the controller to lower the limit, but move the penalty for lowering the limit to the affected cgroups instead of making the controlling process block, especially when changing a lot of limits dynamically this can make a difference. Kind regards, ~Maarten Lankhorst
