[tip:sched/core] sched: Add USER_SCHED to feature removal list
From: tip-bot for Dhaval Giani
Date: Wed Nov 04 2009 - 10:25:44 EST
Author: Dhaval Giani <dhaval@xxxxxxxxxxxxxxxxxx>
AuthorDate: Wed, 4 Nov 2009 03:15:44 +0530
Committer: Ingo Molnar <mingo@xxxxxxx>
CommitDate: Wed, 4 Nov 2009 12:40:26 +0100
sched: Add USER_SCHED to feature removal list
Peter Zijlstra suggested that we remove USER_SCHED at:
Removing USER_SCHED removes a lot of code from the scheduler
and simplifies the code.
We already have the ability to do user based classification
which is tightened using PAM in userspace.
Schedule USER_SCHED for removal in 2.6.34
Signed-off-by: Dhaval Giani <dhaval@xxxxxxxxxxxxxxxxxx>
Acked-by: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
Cc: Balbir Singh <balbir@xxxxxxxxxx>
Cc: Bharata B Rao <bharata@xxxxxxxxxxxxxxxxxx>
Cc: Serge E. Hallyn <serue@xxxxxxxxxx>
Cc: Srivatsa Vaddagiri <vatsa@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
Documentation/feature-removal-schedule.txt | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index bc693ff..f613df8 100644
@@ -6,6 +6,21 @@ be removed from this file.
+Why: USER_SCHED was implemented as a proof of concept for group scheduling.
+ The effect of USER_SCHED can already be achieved from userspace with
+ the help of libcgroup. The removal of USER_SCHED will also simplify
+ the scheduler code with the removal of one major ifdef. There are also
+ issues USER_SCHED has with USER_NS. A decision was taken not to fix
+ those and instead remove USER_SCHED. Also new group scheduling
+ features will not be implemented for USER_SCHED.
+Who: Dhaval Giani <dhaval@xxxxxxxxxxxxxxxxxx>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/