Hi, > > # mount -t cgroup -o bio none /cgroup/bio > > > > Then, you make new bio cgroups and put some processes in them. > > > > # mkdir /cgroup/bio/bgroup1 > > # mkdir /cgroup/bio/bgroup2 > > # echo 1234 /cgroup/bio/bgroup1/tasks > > # echo 5678 /cgroup/bio/bgroup1/tasks > > > > Now you check the ids of the bio cgroups which you just created. > > > > # cat /cgroup/bio/bgroup1/bio.id > > 1 > > # cat /cgroup/bio/bgroup2/bio.id > > 2 > > > > Finally, you can attach the cgroups to "ioband1" and assign them weights. > > > > # dmsetup message ioband1 0 type cgroup > > # dmsetup message ioband1 0 attach 1 > > # dmsetup message ioband1 0 attach 2 > > # dmsetup message ioband1 0 weight 1:30 > > # dmsetup message ioband1 0 weight 2:60 > > > > You can find the manual of dm-ioband at > > http://people.valinux.co.jp/~ryov/dm-ioband/manual/index.html. > > But the user interface for the bio cgroup is temporal and it will be > > changed after the io_context support. > > > I'm grad if these some kinds of params rather than 'id' are also shown > under cgroup. You mean each bio cgroup has to have a lot of files which shows the status of the cgroup or allows you to control the cgroup. I think this should be done after the cgroup bio subsystem supports io_context since the interface will be changed to support it. > Thanks, > -Kame Thank you, Hirokazu Takahashi. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers