Hello, On Mon, Apr 20, 2020 at 07:03:18PM +0200, Michal Hocko wrote: > I have asked about the semantic of this know already and didn't really > get any real answer. So how does swap.high fit into high limit semantic > when it doesn't act as a limit. Considering that we cannot reclaim swap > space I find this really hard to grasp. memory.high slow down is for the case when memory reclaim can't be depended upon for throttling, right? This is the same. Swap can't be reclaimed so the backpressure is applied by slowing down the source, the same way memory.high does. It fits together with memory.low in that it prevents runaway anon allocation when swap can't be allocated anymore. It's addressing the same problem that memory.high slowdown does. It's just a different vector. Thanks. -- tejun
