On Thu, May 04, 2023 at 10:02:38AM -0700, Shakeel Butt wrote: > On Wed, May 3, 2023 at 3:15 PM Chris Li <chrisl@xxxxxxxxxx> wrote: > [...] > > 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. > > What is the exact problem this proposal is solving? Is it the zombie > memcgs? To me that is just a side effect of memory shared between > different memcgs. I am trying to get rid of zombie memcgs by using shared memory controllers. That means also finding alternattive solution for "memcg=" usage. > > > 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. > > What is the iteration of the reparenting? Are you referring to > reparenting the LRUs or something else? Yes, reparenting the LRU. As Yu point out to me offlined. That LRU iteration is on an offline memcg so it shouldn't block any thing major. Still, I think the smemcg offer more than recharging regarding modeling the share relationship. > > > > = 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. > > I am confused by the relationship between shared memory controller and > the underlying shared memory. What does the same life cycle mean? Are Same life cycle means, if the smemcg comes from a tmpfs, the smemcg have the same life cycle of the tmpfs. > the users expected to register the shared memory objects with the > smemcg? What about unnamed shared memory objects like MAP_SHARED or The user doesn't need to register shared memory objects. However the file system code might need to. But I count that as the kernel not the user. The cgroup admin adds the smemcg into the memcg that shares it. We can also make an policy option for kernel auto add by smemcg to memcg that share from it. > memfds? Each file system mount will have their own smemcg. > > How does the charging work for smemcg? Is this new controller hierarchical? Charge only happen once on the smemcg. Please see this thread for the distinguishing between charge counter and borrow counter. https://lore.kernel.org/linux-mm/CALvZod4=+ANT6UR5h7Cp+0hKkVx6tPAaRa5iqBF=L2VBdMKERQ@xxxxxxxxxxxxxx/T/#m955cab80f70097d7c9a5be21c19c4851170fa052 I haven't give too much thought of the hierarchical issue. My initial thought are on the smemcg side, those are not hierarchical. On the memcg side, they are. Do you have specific examples where we can discuss hierarchical usage? > > 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. > > Is the charge of the underlying shared memory live with smemcg or the > memcg where smemcg is attached? Can a smemcg detach and reattach to a Charge live with smemcg. > different memcg? Smemcg can add to more than one memcg without detached. Please see the above email regarding borrow vs charge. > > > 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. > > The above is somewhat giving the impression that the charge of shared > memory lives with smemcg. This can mess up or complicate the > hierarchical property of the original memcg. I haven't given a lot of thought to that. Can you share with me an example how things can mess up? I will see if I can use the smemcg model to address it. > > 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. > > The OOM killing for remote charging needs much more thought. Please > see https://lwn.net/Articles/787626/ for previous discussion on > related topic. Yes, just take a look. I think the new idea is borrow vs charged. Let's come up with some detail example try to break the smemcg borrow model. Chris
