summaryrefslogtreecommitdiff
path: root/include/linux/bpf-cgroup.h
diff options
context:
space:
mode:
authorShakeel Butt <shakeelb@google.com>2021-10-25 09:19:16 +0300
committerTejun Heo <tj@kernel.org>2021-10-25 20:26:00 +0300
commit822bc9bac9e9a2f76a772a34f745962dfc223353 (patch)
treec6899104e273f2537d1e3951d578a2b6069eb2ca /include/linux/bpf-cgroup.h
parentbb758421416fd8af2267a8e07d53fb8328b07c4e (diff)
downloadlinux-822bc9bac9e9a2f76a772a34f745962dfc223353.tar.xz
cgroup: no need for cgroup_mutex for /proc/cgroups
On the real systems, the cgroups hierarchies are setup early and just once by the node controller, so, other than number of cgroups, all information in /proc/cgroups remain same for the system uptime. Let's remove the cgroup_mutex usage on reading /proc/cgroups. There is a chance of inconsistent number of cgroups for co-mounted cgroups while printing the information from /proc/cgroups but that is not a big issue. In addition /proc/cgroups is a v1 specific interface, so the dependency on it should reduce over time. The main motivation for removing the cgroup_mutex from /proc/cgroups is to reduce the avenues of its contention. On our fleet, we have observed buggy application hammering on /proc/cgroups and drastically slowing down the node controller on the system which have many negative consequences on other workloads running on the system. Signed-off-by: Shakeel Butt <shakeelb@google.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'include/linux/bpf-cgroup.h')
0 files changed, 0 insertions, 0 deletions