On Thu, Dec 26, 2019 at 02:56:40PM +0800, teawater wrote: > For example, an application does a lot of file access work in a > memory-constrained environment. > [...] > Both of them are extreme examples. The examples are quite generic. Do cgroup v2 controls really prevent handling such workloads appropriately? Besides that, note that per-cgroup swappiness as used in v1 cannot be simply transferred into v2 because, it's a concept that doesn't take into account cgroup hierarchies (how would parent's swappiness affect children? what would swappiness on inner nodes mean?). HTH, Michal