On Thu 21-05-20 12:27:11, Chris Down wrote: [...] > Regardless, you're pushing for different reclaim semantics for memory.high > than memory.max here, which requires evidence that the current approach > taken for memory.max is wrong or causing issues. Sorry, I have skipped over this part. Memory high limit reclaim has historically acted as a best effort action to throttle the allocation/charge pace. This would work both if the implementation simply tried to reclaim down to the high limit or if the reclaim is proportional to the memory consumption by a specific consumer. We do the later because it is much easier to establish fairness for. If you want to change that you somehow have to deal with the fairness problem. And yes, we do not guarantee any fairness for the hard limit or direct reclaim in general but that behavior is generally problematic and there should be really strong arguments to move high limit reclaim that direction IMHO. -- Michal Hocko SUSE Labs
