On Mon, 2015-05-04 at 08:54 +0800, Zefan Li wrote:
> It's allowed to promote a task from normal to realtime after it has been
> attached to a non-root cgroup, but it will fail if the attaching happens
> after it has become realtime. I don't see how this restriction is useful.
In the CONFIG_RT_GROUP_SCHED case, promotion will fail is there is no
bandwidth allocated.
> We are moving toward unified hierarchy where all the cgroup controllers
> are bound together, so it would make cgroups easier to use if we have less
> restrictions on attaching tasks between cgroups.
Forcing group scheduling overhead on users if they want cpuset or memory
cgroup functionality would be far from wonderful. Am I interpreting the
implications of this unification/binding properly?
(I hope not, surely the plan is not to utterly _destroy_ cgroup utility)
-Mike
--
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/
