Giuseppe Scrivano <gscrivan@xxxxxxxxxx> writes: > In the effort of supporting cgroups v2 into Kubernetes, I stumped on > the lack of the hugetlb controller. > > When the controller is enabled, it exposes three new files for each > hugetlb size on non-root cgroups: > > - hugetlb.<hugepagesize>.current > - hugetlb.<hugepagesize>.max > - hugetlb.<hugepagesize>.events > - hugetlb.<hugepagesize>.events.local > > The differences with the legacy hierarchy are in the file names and > using the value "max" instead of "-1" to disable a limit. > > The file .limit_in_bytes is renamed to .max. > > The file .usage_in_bytes is renamed to .usage. > > .failcnt is not provided as a single file anymore, but its value can > be read through the new flat-keyed files .events and .events.local, > through the "max" key. > > Signed-off-by: Giuseppe Scrivano <gscrivan@xxxxxxxxxx> > --- > v4: > - fix .events file to record and notify all the events in the sub > directories > - add .events.local file to record events only in the current cgroup > > v3: https://www.spinics.net/lists/cgroups/msg23922.html > - simplify hugetlb_cgroup_read_u64_max and drop dead code > - notify changes to the .events file > > v2: https://www.spinics.net/lists/cgroups/msg23917.html > - dropped max_usage_in_bytes and renamed .stats::failcnt to .events::max > > v1: https://www.spinics.net/lists/cgroups/msg23893.html is there anything I could do to move this forward? Thanks, Giuseppe
