From a80ec8d5b4e4df8f33122d9d67f4947c4bb6d09c Mon Sep 17 00:00:00 2001 From: Alexander Kuleshov Date: Mon, 20 Nov 2017 00:25:17 +0600 Subject: [PATCH] fix #546 --- Cgroups/cgroups1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Cgroups/cgroups1.md b/Cgroups/cgroups1.md index f620494..61524ae 100644 --- a/Cgroups/cgroups1.md +++ b/Cgroups/cgroups1.md @@ -277,7 +277,7 @@ struct cgroup_subsys { Where for example `ccs_online` and `ccs_offline` callbacks are called after a cgroup successfully will complete all allocations and a cgroup will be before releasing respectively. The `early_init` flags marks subsystems which may/should be initialized early. The `id` and `name` fields represents unique identifier in the array of registered subsystems for a cgroup and `name` of a subsystem respectively. The last - `root` fields represents pointer to the root of of a cgroup hierarchy. -Of course the `cgroup_subsys` structure bigger and has other fields, but it is enough for now. Now as we got to know important structures related to `cgroups` mechanism, let's return to the `cgroup_init_early` function. Main purpose of this function is to do early initialization of some subsystems. As you already may guess, these `early` subsystems should have `cgroup_subsys->early_init = 1`. Let's look what subsystems may be initialized early. +Of course the `cgroup_subsys` structure is bigger and has other fields, but it is enough for now. Now as we got to know important structures related to `cgroups` mechanism, let's return to the `cgroup_init_early` function. Main purpose of this function is to do early initialization of some subsystems. As you already may guess, these `early` subsystems should have `cgroup_subsys->early_init = 1`. Let's look what subsystems may be initialized early. After the definition of the two local variables we may see following lines of code: