Messages in this thread |  | | | Date | Thu, 8 Mar 2012 13:22:45 -0500 | | From | Vivek Goyal <> | | Subject | Re: [PATCHSET] mempool, percpu, blkcg: fix percpu stat allocation and remove stats_lock |
| |
On Thu, Mar 08, 2012 at 10:11:25AM -0800, Tejun Heo wrote: > On Thu, Mar 08, 2012 at 10:08:33AM -0800, Tejun Heo wrote: > > It's probably from something forgetting to put cgroup and pre_destroy > > waiting for it. Such bugs would have been masked before but now show > > up as stalls during rmdir. I'm not too happy with how cgroup is > > handling cgroup file additions and removals and hoping to implement > > proper 'sever' semantics similar to that of sysfs. In the longer > > term, such behavior should go away but for now we'll just have to hunt > > down the actual bug to avoid stalls (which we have to do anyway but > > it's more visible now). > > Hmm... I'll probably need it for dynamic file additions and removals > for dynamic policy updates && the blkcg changes are scheduled for > 3.5-rc1 window (not 3.4-rc1), so we should have enough time to resolve > this.
Does that mean in 3.4 we will continue to kill throttling groups and lose all the policies and stats upon elevator change? So 3.4 will be one odd release w.r.t this user visible change.
Thanks Vivek
|  |