On Wed, 3 Sept 2025 at 00:23, Christian König <christian.koe...@amd.com> wrote: > > On 02.09.25 06:06, Dave Airlie wrote: > > From: Dave Airlie <airl...@redhat.com> > > > > This enables all the backend code to use the list lru in memcg mode, > > and set the shrinker to be memcg aware. > > > > It adds the loop case for when pooled pages end up being reparented > > to a higher memcg group, that newer memcg can search for them there > > and take them back. > > I can only repeat that as far as I can see that makes no sense at all. > > This just enables stealing pages from the page pool per cgroup and won't give > them back if another cgroup runs into a low memery situation. > > Maybe Thomas and the XE guys have an use case for that, but as far as I can > see that behavior is not something we would ever want.
This is what I'd want for a desktop use case at least, if we have a top level cgroup then logged in user cgroups, each user will own their own uncached pages pool and not cause side effects to other users. If they finish running their pool will get give to the parent. Any new pool will get pages from the parent, and manage them itself. This is also what cgroup developers have said makes the most sense for containerisation here, one cgroup allocator should not be able to cause shrink work for another cgroup unnecessarily. Dave.
