Skip to content

RFC Generic container system

[email protected] lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest4 patches 9 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4Generic container system abstracted from cpusets codeDocumentation/containers.txt fs/proc/base.c include/linux/container.h +8 more+1709 -14 replies
2/4Cpusets hooked into containersDocumentation/cpusets.txt fs/proc/base.c include/linux/container.h +8 more+228 -12901 reply
3/4Add generic multi-subsystem API to containersDocumentation/containers.txt include/linux/container.h include/linux/cpuset.h +2 more+269 -830 replies
4/4Simple CPU accounting container subsysteminclude/linux/cpu_acct.h init/Kconfig kernel/Makefile +2 more+129 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC][PATCH 0/4] Generic container system

There have recently been various proposals floating around for resource management/accounting subsystems in the kernel, including Res Groups, User BeanCounters and others. These all need the basic abstraction of being able to group together multiple processes in an aggregate, in order to track/limit the resources permitted to those processes, and all implement this grouping in different ways.

Already existing in the kernel is the cpuset subsystem; this has a process grouping mechanism that is mature, tested, and well documented (particularly with regards to synchronization rules).

This patchset extracts the process grouping code from cpusets into a generic container system, and makes the cpusets code a client of the container system.

It also provides a very simple additional container subsystem to do per-container CPU usage accounting; this is primarily to demonstrate use of the container subsystem API, but is useful in its own right.

The change is implemented in four stages:

1) extract the process grouping code from cpusets into a standalone system

2) remove the process grouping code from cpusets and hook into the container system

3) convert the container system to present a generic API, and make cpusets a client of that API

4) add a simple CPU accounting container subsystem

The intention is that the various resource management efforts can also become container clients, with the result that:

- the userspace APIs are (somewhat) normalised

- it's easier to test out e.g. the ResGroups CPU controller in conjunction with the UBC memory controller

- the additional kernel footprint of any of the competing resource management systems is substantially reduced, since it doesn't need to provide process grouping/containment, hence improving their chances of getting into the kernel

Possible TODOs include:

- define a convention for populating the per-container directories so that different subsystems don't clash with one another

- provide higher-level primitives (e.g. an easy interface to seq_file) for files registered by subsystems.

- support subsystem deregistering

---