Messages in this thread | | | Date | Fri, 8 Apr 2022 10:55:56 -0400 | From | Dan Schatzberg <> | Subject | Re: [PATCH v3 1/4] memcg: introduce per-memcg reclaim interface |
| |
On Fri, Apr 08, 2022 at 04:11:05PM +0200, Michal Hocko wrote: > Regarding "max" as a possible input. I am not really sure to be honest. > I can imagine that it could be legit to simply reclaim all the charges > (e.g. before removing the memcg) which should be achieveable by > reclaiming the reported consumption. Or what exactly should be the > semantic?
Yeah, it just allows you to avoid reading memory.current to just reclaim everything if you can specify "max" - you're still protected by nretries to eventually bail out. Mostly, though I just feel like supporting "max" makes memory.reclaim semetric with a lot of the cgroup memory control files which tend to support "max".
| |