On Thu 27-09-12 10:46:05, Tejun Heo wrote: [...] > > > The part I nacked is enabling kmemcg on a populated cgroup and then > > > starting accounting from then without any apparent indication that any > > > past allocation hasn't been considered. You end up with numbers which > > > nobody can't tell what they really mean and there's no mechanism to > > > guarantee any kind of ordering between populating the cgroup and > > > configuring it and there's *no* way to find out what happened > > > afterwards neither. This is properly crazy and definitely deserves a > > > nack. > > > > > > > Mel suggestion of not allowing this to happen once the cgroup has tasks > > takes care of this, and is something I thought of myself. > > You mean Michal's? It should also disallow switching if there are > children cgroups, right? Right. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
