On Thu 17-10-24 09:04:37, Joshua Hahn wrote: > HugeTLB usage is a metric that can provide utility for monitors hoping > to get more insight into the memory usage patterns in cgroups. It also > helps identify if large folios are being distributed efficiently across > workloads, so that tasks that can take most advantage of reduced TLB > misses are prioritized. > > While cgroupv2's hugeTLB controller does report this value, some users > who wish to track hugeTLB usage might not want to take on the additional > overhead or the features of the controller just to use the metric. > This patch introduces hugeTLB usage in the memcg stats, mirroring the > value in the hugeTLB controller and offering a more fine-grained > cgroup-level breakdown of the value in /proc/meminfo. This seems really confusing because memcg controller is not responsible for the hugetlb memory. Could you be more specific why enabling hugetlb controller is not really desirable when the actual per-group tracking is needed? > Signed-off-by: Joshua Hahn <joshua.hahnjy@xxxxxxxxx> > > Joshua Hahn (1): > Adding hugeTLB counters to memory controller > > include/linux/memcontrol.h | 3 +++ > mm/hugetlb.c | 5 +++++ > mm/memcontrol.c | 6 ++++++ > 3 files changed, 14 insertions(+) > > -- > 2.43.5 -- Michal Hocko SUSE Labs
