On Wed, 20.07.11 17:26, Vivek Goyal (vgoyal@xxxxxxxxxx) wrote: > > /sys/fs/cgroup/cpu+cpuacct is the joint mount point. > > > > /sys/fs/cgroup/cpu → /sys/fs/cgroup/cpu+cpuacct is a symlink. > > > > /sys/fs/cgroup/cpuacct → /sys/fs/cgroup/cpu+cpuacct is a symlink. > > > > That way to most applications it will be very easy to support this: they > > can simply assume that the controller "foobar" is available under > > /sys/fs/cgroup/foobar, and that's it. > > I guess this will be reasonable. Just that application need to handle > the case that directory they are about to create might already be present > there. systemd always uses to equivalent of "mkdir -p" to create its groups. So at least systemd should be safe here. > So down the we should be able to co-mount memory and IO together with > additional symlinks? Yes, if you wish. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
