Hi T.J., On Tue, Apr 11, 2023 at 04:36:37PM -0700, T.J. Mercier wrote: > When a memcg is removed by userspace it gets offlined by the kernel. > Offline memcgs are hidden from user space, but they still live in the > kernel until their reference count drops to 0. New allocations cannot > be charged to offline memcgs, but existing allocations charged to > offline memcgs remain charged, and hold a reference to the memcg. > > As such, an offline memcg can remain in the kernel indefinitely, > becoming a zombie memcg. The accumulation of a large number of zombie > memcgs lead to increased system overhead (mainly percpu data in struct > mem_cgroup). It also causes some kernel operations that scale with the > number of memcgs to become less efficient (e.g. reclaim). > > There are currently out-of-tree solutions which attempt to > periodically clean up zombie memcgs by reclaiming from them. However > that is not effective for non-reclaimable memory, which it would be > better to reparent or recharge to an online cgroup. There are also > proposed changes that would benefit from recharging for shared > resources like pinned pages, or DMA buffer pages. I am also interested in this topic. T.J. and I have some offline discussion about this. We have some proposals to solve this problem. I will share the write up here for the up coming LSF/MM discussion. Shared Memory Cgroup Controllers = Introduction The current memory cgroup controller does not support shared memory objects. For the memory that is shared between different processes, it is not obvious which process should get charged. Google has some internal tmpfs “memcg=” mount option to charge tmpfs data to a specific memcg that’s often different from where charging processes run. However it faces some difficulties when the charged memcg exits and the charged memcg becomes a zombie memcg. Other approaches include “re-parenting” the memcg charge to the parent memcg. Which has its own problem. If the charge is huge, iteration of the reparenting can be costly. = Proposed Solution The proposed solution is to add a new type of memory controller for shared memory usage. E.g. tmpfs, hugetlb, file system mmap and dma_buf. This shared memory cgroup controller object will have the same life cycle of the underlying shared memory. Processes can not be added to the shared memory cgroup. Instead the shared memory cgroup can be added to the memcg using a “smemcg” API file, similar to adding a process into the “tasks” API file. When a smemcg is added to the memcg, the amount of memory that has been shared in the memcg process will be accounted for as the part of the memcg “memory.current”.The memory.current of the memcg is make up of two parts, 1) the processes anonymous memory and 2) the memory shared from smemcg. When the memcg “memory.current” is raised to the limit. The kernel will active try to reclaim for the memcg to make “smemcg memory + process anonymous memory” within the limit. Further memory allocation within those memcg processes will fail if the limit can not be followed. If many reclaim attempts fail to bring the memcg “memory.current” within the limit, the process in this memcg will get OOM killed. = Benefits The benefits of this solution include: * No zombie memcg. The life cycle of the smemcg match the share memory file system or dma_buf. * No reparenting. The shared memory only charge once to the smemcg object. A memcg can include a smemcg to as part of the memcg memory usage. When process exit and memcg get deleted, the charge remain to the smemcg object. * Much cleaner mental model of the smemcg, each share memory page is charge to one smemcg only once. * Notice the same smemcg can add to more than one memcg. It can better describe the shared memory relation. Chris > Suggested attendees: > Yosry Ahmed <yosryahmed@xxxxxxxxxx> > Yu Zhao <yuzhao@xxxxxxxxxx> > T.J. Mercier <tjmercier@xxxxxxxxxx> > Tejun Heo <tj@xxxxxxxxxx> > Shakeel Butt <shakeelb@xxxxxxxxxx> > Muchun Song <muchun.song@xxxxxxxxx> > Johannes Weiner <hannes@xxxxxxxxxxx> > Roman Gushchin <roman.gushchin@xxxxxxxxx> > Alistair Popple <apopple@xxxxxxxxxx> > Jason Gunthorpe <jgg@xxxxxxxxxx> > Kalesh Singh <kaleshsingh@xxxxxxxxxx> >
