> Hi, > > > > > On Wed, Jan 23, 2008 at 09:53:50PM +0900, Ryo Tsuruta wrote: > > > > > Dm-band gives bandwidth to each job according to its weight, > > > > > which each job can set its own value to. > > > > > At this time, a job is a group of processes with the same pid or pgrp > > > > > or uid. > > > > > > > > It seems to rely on 'current' to classify bios and doesn't do it until > > > > the map > > > > function is called, possibly in a different process context, so it won't > > > > always identify the original source of the I/O correctly: > > > > > > Yes, this should be mentioned in the document with the current > > > implementation > > > as you pointed out. > > > > > > By the way, I think once a memory controller of cgroup is introduced, it > > > will > > > help to track down which cgroup is the original source. > > > > do you mean to make this a part of the memory subsystem? > > I just think if the memory subsystem is in front of us, we don't need to > reinvent the wheel. > > But I don't have a concrete image how the interface between dm-band and > the memory subsystem should be designed yet. I'd be appreciate if some of > the cgroup developers give some ideas about it.
the current implementation of memory subsystem associates pages to cgroups directly, rather than via tasks. so it isn't straightforward to use the information for other classification mechanisms like yours which might not share the view of "hierarchy" with the memory subsystem. YAMAMOTO Takashi > > Thanks, > Hirokazu Takahashi. > > > > YAMAMOTO Takashi _______________________________________________ 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
