what difference bettween /sys/fs/cgroup/systemd/ && /sys/fs/cgroup/xxx/
I know that ./systemd-219/src/core/mount-setup.c define some cgroup mount path .
But I do not know why systemd create directory /sys/fs/cgroup/systemd/ and what's difference between /sys/fs/cgroup/systemd/ and /sys/fs/cgroup/memory/?
Is /sys/fs/cgroup/systemd/ mount path just mean default cgroup path?
#ll /sys/fs/cgroup/systemd/
total 0
-rw-r--r-- 1 root root 0 Jul 6 2017 cgroup.clone_children
--w--w--w- 1 root root 0 Jul 6 2017 cgroup.event_control
-rw-r--r-- 1 root root 0 Jul 6 15:24 cgroup.procs
-r--r--r-- 1 root root 0 Jul 6 2017 cgroup.sane_behavior
drwxr-xr-x 3 root root 0 Jul 6 15:23 docker.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 notify_on_release
-rw-r--r-- 1 root root 0 Jul 6 2017 release_agent
drwxr-xr-x 65 root root 0 Jul 6 15:38 system.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 tasks
drwxr-xr-x 4 root root 0 Jul 6 21:18 user.slice
systemd
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
add a comment |
I know that ./systemd-219/src/core/mount-setup.c define some cgroup mount path .
But I do not know why systemd create directory /sys/fs/cgroup/systemd/ and what's difference between /sys/fs/cgroup/systemd/ and /sys/fs/cgroup/memory/?
Is /sys/fs/cgroup/systemd/ mount path just mean default cgroup path?
#ll /sys/fs/cgroup/systemd/
total 0
-rw-r--r-- 1 root root 0 Jul 6 2017 cgroup.clone_children
--w--w--w- 1 root root 0 Jul 6 2017 cgroup.event_control
-rw-r--r-- 1 root root 0 Jul 6 15:24 cgroup.procs
-r--r--r-- 1 root root 0 Jul 6 2017 cgroup.sane_behavior
drwxr-xr-x 3 root root 0 Jul 6 15:23 docker.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 notify_on_release
-rw-r--r-- 1 root root 0 Jul 6 2017 release_agent
drwxr-xr-x 65 root root 0 Jul 6 15:38 system.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 tasks
drwxr-xr-x 4 root root 0 Jul 6 21:18 user.slice
systemd
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
add a comment |
I know that ./systemd-219/src/core/mount-setup.c define some cgroup mount path .
But I do not know why systemd create directory /sys/fs/cgroup/systemd/ and what's difference between /sys/fs/cgroup/systemd/ and /sys/fs/cgroup/memory/?
Is /sys/fs/cgroup/systemd/ mount path just mean default cgroup path?
#ll /sys/fs/cgroup/systemd/
total 0
-rw-r--r-- 1 root root 0 Jul 6 2017 cgroup.clone_children
--w--w--w- 1 root root 0 Jul 6 2017 cgroup.event_control
-rw-r--r-- 1 root root 0 Jul 6 15:24 cgroup.procs
-r--r--r-- 1 root root 0 Jul 6 2017 cgroup.sane_behavior
drwxr-xr-x 3 root root 0 Jul 6 15:23 docker.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 notify_on_release
-rw-r--r-- 1 root root 0 Jul 6 2017 release_agent
drwxr-xr-x 65 root root 0 Jul 6 15:38 system.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 tasks
drwxr-xr-x 4 root root 0 Jul 6 21:18 user.slice
systemd
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
I know that ./systemd-219/src/core/mount-setup.c define some cgroup mount path .
But I do not know why systemd create directory /sys/fs/cgroup/systemd/ and what's difference between /sys/fs/cgroup/systemd/ and /sys/fs/cgroup/memory/?
Is /sys/fs/cgroup/systemd/ mount path just mean default cgroup path?
#ll /sys/fs/cgroup/systemd/
total 0
-rw-r--r-- 1 root root 0 Jul 6 2017 cgroup.clone_children
--w--w--w- 1 root root 0 Jul 6 2017 cgroup.event_control
-rw-r--r-- 1 root root 0 Jul 6 15:24 cgroup.procs
-r--r--r-- 1 root root 0 Jul 6 2017 cgroup.sane_behavior
drwxr-xr-x 3 root root 0 Jul 6 15:23 docker.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 notify_on_release
-rw-r--r-- 1 root root 0 Jul 6 2017 release_agent
drwxr-xr-x 65 root root 0 Jul 6 15:38 system.slice
-rw-r--r-- 1 root root 0 Jul 6 2017 tasks
drwxr-xr-x 4 root root 0 Jul 6 21:18 user.slice
systemd
systemd
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
edited Jul 8 '17 at 8:49
Ortomala Lokni
2,21511442
2,21511442
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
asked Jul 6 '17 at 13:21
穆阿浩穆阿浩
106315
106315
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Systemd 219 uses the Linux kernel cgroup v1 feature and mounts multiple hierarchies under /sys/fs/cgroup, some for controllers, some without.
/sys/fs/cgroup/systemd is a hierarchy without croup controllers, just for systemd usage (tracking which processes are part of which cgroups).
This will change once the migration to cgroup v2 is complete and there will be only one cgroup hierarchy (unified hierarchy).
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
But even withcgroup_no_v1=allsystem/sys/fs/cgroup/systemdstill exist.
– 炸鱼薯条德里克
Feb 6 at 5:19
If you want systemd to only use the new v2 hierarchy, you should set systemd.unified_cgroup_hierarchy to true on the kernel command line. Those options may differ depending on your systemd version.
– Siosm
Feb 7 at 7:53
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f375757%2fwhat-difference-bettween-sys-fs-cgroup-systemd-sys-fs-cgroup-xxx%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Systemd 219 uses the Linux kernel cgroup v1 feature and mounts multiple hierarchies under /sys/fs/cgroup, some for controllers, some without.
/sys/fs/cgroup/systemd is a hierarchy without croup controllers, just for systemd usage (tracking which processes are part of which cgroups).
This will change once the migration to cgroup v2 is complete and there will be only one cgroup hierarchy (unified hierarchy).
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
But even withcgroup_no_v1=allsystem/sys/fs/cgroup/systemdstill exist.
– 炸鱼薯条德里克
Feb 6 at 5:19
If you want systemd to only use the new v2 hierarchy, you should set systemd.unified_cgroup_hierarchy to true on the kernel command line. Those options may differ depending on your systemd version.
– Siosm
Feb 7 at 7:53
add a comment |
Systemd 219 uses the Linux kernel cgroup v1 feature and mounts multiple hierarchies under /sys/fs/cgroup, some for controllers, some without.
/sys/fs/cgroup/systemd is a hierarchy without croup controllers, just for systemd usage (tracking which processes are part of which cgroups).
This will change once the migration to cgroup v2 is complete and there will be only one cgroup hierarchy (unified hierarchy).
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
But even withcgroup_no_v1=allsystem/sys/fs/cgroup/systemdstill exist.
– 炸鱼薯条德里克
Feb 6 at 5:19
If you want systemd to only use the new v2 hierarchy, you should set systemd.unified_cgroup_hierarchy to true on the kernel command line. Those options may differ depending on your systemd version.
– Siosm
Feb 7 at 7:53
add a comment |
Systemd 219 uses the Linux kernel cgroup v1 feature and mounts multiple hierarchies under /sys/fs/cgroup, some for controllers, some without.
/sys/fs/cgroup/systemd is a hierarchy without croup controllers, just for systemd usage (tracking which processes are part of which cgroups).
This will change once the migration to cgroup v2 is complete and there will be only one cgroup hierarchy (unified hierarchy).
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
Systemd 219 uses the Linux kernel cgroup v1 feature and mounts multiple hierarchies under /sys/fs/cgroup, some for controllers, some without.
/sys/fs/cgroup/systemd is a hierarchy without croup controllers, just for systemd usage (tracking which processes are part of which cgroups).
This will change once the migration to cgroup v2 is complete and there will be only one cgroup hierarchy (unified hierarchy).
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
answered Mar 11 '18 at 10:53
SiosmSiosm
649612
649612
But even withcgroup_no_v1=allsystem/sys/fs/cgroup/systemdstill exist.
– 炸鱼薯条德里克
Feb 6 at 5:19
If you want systemd to only use the new v2 hierarchy, you should set systemd.unified_cgroup_hierarchy to true on the kernel command line. Those options may differ depending on your systemd version.
– Siosm
Feb 7 at 7:53
add a comment |
But even withcgroup_no_v1=allsystem/sys/fs/cgroup/systemdstill exist.
– 炸鱼薯条德里克
Feb 6 at 5:19
If you want systemd to only use the new v2 hierarchy, you should set systemd.unified_cgroup_hierarchy to true on the kernel command line. Those options may differ depending on your systemd version.
– Siosm
Feb 7 at 7:53
But even with
cgroup_no_v1=all system /sys/fs/cgroup/systemd still exist.– 炸鱼薯条德里克
Feb 6 at 5:19
But even with
cgroup_no_v1=all system /sys/fs/cgroup/systemd still exist.– 炸鱼薯条德里克
Feb 6 at 5:19
If you want systemd to only use the new v2 hierarchy, you should set systemd.unified_cgroup_hierarchy to true on the kernel command line. Those options may differ depending on your systemd version.
– Siosm
Feb 7 at 7:53
If you want systemd to only use the new v2 hierarchy, you should set systemd.unified_cgroup_hierarchy to true on the kernel command line. Those options may differ depending on your systemd version.
– Siosm
Feb 7 at 7:53
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f375757%2fwhat-difference-bettween-sys-fs-cgroup-systemd-sys-fs-cgroup-xxx%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
