Comment 13 for bug 188226

Re-opening as discussed on IRC with dhaval and Tim.

For the record: CONFIG_FAIR_CGROUP_SCHED is arch independent.

As dhaval pointed out, using cgroups (and the previous behaviour) would save us a lot of bug reports in the future, like e.g. bug 177713, where a process running in the background gets 50% of all cpu cycles at least.

I repeat, using CONFIG_FAIR_USER_SCHED is especially bad on the desktop: processes running as another user (especially root, which gets twice as much cpu shares as other users by default) will slow the current user's processes down.

With cgroups, you _can_ put a daemon in place, but you don't have to.
Using cgroups without any daemon/hooking will just result in the pre-Hardy behavior: all processes are in the same pool for cpu shares.
But, in contrast to CONFIG_FAIR_USER_SCHED, CONFIG_FAIR_CGROUP_SCHED allows much finer control of resources, if you want to setup this manually.