On Mon, May 18, 2015 at 12:34:40PM -0400, Tejun Heo wrote: > On Wed, May 13, 2015 at 04:35:15PM -0400, Tejun Heo wrote: > > threadgroup locking was added because cgroup needs threadgroups to > > stay stable across attach operations. It was implemented as a > > per-signal_struct generic locking mechanism so that other users which > > require threadgroups stable across blocking operations can use it too; > > however, it hasn't grown any other use cases and still conditionalized > > on CONFIG_CGROUPS. > > Ingo, Peter, what do you guys think?
I had a brief look and didn't spot anhything really weird. I'll try and give is a little more time tomorrow. On routing I think you can take it through the cgroup tree if Ingo is ok with that. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
