On Thu, Aug 18, 2022 at 12:20:33PM -1000, Tejun Heo wrote: > We have the exact same problem for any resources which span multiple > instances of a service including page cache, tmpfs instances and any other > thing which can persist longer than procss life time. My current opinion is To expand a bit more on this point, once we start including page cache and tmpfs, we now get entangled with memory reclaim which then brings in IO and not-yet-but-eventually CPU usage. Once you start splitting the tree like you're suggesting here, all those will break down and now we have to worry about how to split resource accounting and control for the same entities across two split branches of the tree, which doesn't really make any sense. So, we *really* don't wanna paint ourselves into that kind of a corner. This is a dead-end. Please ditch it. Thanks. -- tejun
