On 2016/6/21 16:34, Ma Shimiao wrote: > Hi Rosen, > On 06/21/2016 03:38 PM, Rosen, Rami wrote: >> Hi, Ma, >> >>> Ah, it seems work, but I'm not sure. >> >>>> Then, I executed: >>>> # mount -t cgroup2 none /mnt >> >> It should work. The thing is, according to my trials from the past, it could be that systemd triggers mounting of cgroup V1 controllers. When I made trials with cgroup v2, eventually I turned on to disros which do not run systemd (namely, it was Ubuntu. You can set Ubuntu not to use systemd, even in most recent Ubuntu systems, where systemd became the default). >> >> What happens if you mount cgroup v2 now, after booting with cgroup_no_v1=all: >> mount -t cgroup2 none /mnt >> >> And then try to unmount cgroup v1 controllers like memory ? >> Do you see anything under /mnt? > > Yes, after booting with cgroup_no_v1, then execute > #mount -t cgroup2 none /mnt > #cat /mnt/cgroup.controllers > io memory > > There are controllers io and memory. > But, cgroup2 is not mounted in the system by default? because systemd hasn't supported cgroup2 yet. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
