On Fri, Apr 17, 2009 at 10:24:17AM +0900, KAMEZAWA Hiroyuki wrote: > On Tue, 14 Apr 2009 22:21:12 +0200 > Andrea Righi <righi.and...@gmail.com> wrote: > > > +Example: > > +* Create an association between an io-throttle group and a bio-cgroup group > > + with "bio" and "blockio" subsystems mounted in different mount points: > > + # mount -t cgroup -o bio bio-cgroup /mnt/bio-cgroup/ > > + # cd /mnt/bio-cgroup/ > > + # mkdir bio-grp > > + # cat bio-grp/bio.id > > + 1 > > + # mount -t cgroup -o blockio blockio /mnt/io-throttle > > + # cd /mnt/io-throttle > > + # mkdir foo > > + # echo 1 > foo/blockio.bio_id > > Why do we need multiple cgroups at once to track I/O ? > Seems complicated to me. > > Thanks, > -Kame
I totally agree. I could easily merge the bio-cgroup functionality in io-throttle or implement this as an infrastructure framework, using a single controller and remove this complication. For now, since the decisions on IO controllers are not definitive at all, I privileged flexibility and I simply decided to be a plain user of bio-cgroup to quickly adapt my patch to the future bio-cgroup development. Thanks, -Andrea _______________________________________________ Containers mailing list contain...@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list Devel@openvz.org https://openvz.org/mailman/listinfo/devel
