On Wed, 2008-08-06 at 22:12 +0530, Balbir Singh wrote: > Would you like to split up IO into read and write IO. We know that read can be > very latency sensitive when compared to writes. Should we consider them > separately in the RFC?
I'd just suggest doing what is simplest and can be done in the smallest amount of code. As long as it is functional in some way and can be extended to cover the end goal, I say keep it tiny. > > Even in the non-hotplug case it would be nice if we could treat each > > block I/O device as an independent resource, which means we could do > > things like allocating I/O bandwidth on a per-device basis. As long as > > performance is not compromised too much, adding some kind of basic > > hotplug support to cgroups is probably worth it. > > Won't that get too complex. What if the user has thousands of disks with > several > partitions on each? I think what Fernando is suggesting is that we *allow* each disk to be treated separately, not that we actually separate them out. I agree that with large disk count systems, it would get a bit nutty to deal with I/O limits on each of them. It would also probably be nutty for some dude with two disks in his system to have to set (or care about) individual limits. I guess I'm just arguing that we should allow pretty arbitrary grouping of block devices into these resource pools. -- Dave _______________________________________________ Containers mailing list [EMAIL PROTECTED] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list Devel@openvz.org https://openvz.org/mailman/listinfo/devel
