Hey, Matt. On Thu, Oct 18, 2012 at 06:29:45PM -0700, Matt Helsley wrote: > Yeah, that would be a nice cleanup too. I guess the ultra-careful way to > remove this feature would be something like: > > Add an internal migration restriction (which may or may not be > exported as a userspace interface in a subsequent > patch). > > Make the cgroup freezer use it. > > Make the cgroup freezer WARN_ONCE() when the subsystem is first > mounted. Indicates that the behavior is going to > change. > > ... time passes ... > > Remove the use of the migration "lock" from the cgroup freezer > and the WARN_ONCE(). > > Which would also make the feature more obvious.
I don't think I'm gonna go that far for this. I don't think we need cgroup migration locking after all. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
