diff options
| author | Giuseppe Scrivano <gscrivan@redhat.com> | 2019-12-16 20:38:31 +0100 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2019-12-16 12:41:40 -0800 |
| commit | faced7e0806cf44095a2833ad53ff59c39e6748d (patch) | |
| tree | 608f80245f7978cc3d2eeb8fc3be5f2511b6840c /kernel | |
| parent | 6afa873170a612b2b9e392c19c523ed8aae6fbc9 (diff) | |
mm: hugetlb controller for cgroups v2
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 four 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 .current.
.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@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions