View Single Post
Posts: 34 | Thanked: 50 times | Joined on Jun 2010
#272
Originally Posted by epitaph View Post
Out-of-the-box this patch isn't worth to apply you want to add this value to it:

Code:
echo "1" > /dev/cgroup/cpu/desktop/notify_on_release
echo "1" > /dev/cgroup/cpu/applications/notify_on_release
echo "555555" > /dev/cgroup/cpu/cpu.rt_runtime_us
echo "600000" > /dev/cgroup/cpu/cpu.rt_period_us
echo "555555" > /dev/cgroup/cpu/user/cpu.rt_runtime_us
echo "600000" > /dev/cgroup/cpu/user/cpu.rt_period_us
echo "512" > /dev/cgroup/cpu/cpu.shares
echo "512" > /dev/cgroup/cpu/desktop/cpu.shares
echo "512" > /dev/cgroup/cpu/applications/cpu.shares
echo "25M" > /dev/cgroup/cpu/desktop/memory.limit_in_bytes
echo "95M" > /dev/cgroup/cpu/user/memory.limit_in_bytes
Mmmmhm, I see it's tweakable to a fair degree, but the main result automatic process grouping brings is the grouping itself which works well with the kernel's CFS scheduler. Tweaking resource allocation per group will doubtless be worth doing though.

One thing - the rt.period/runtime and memory limit settings do take effect, but these lines :-
echo "512" > /dev/cgroup/cpu/cpu.shares
echo "512" > /dev/cgroup/cpu/desktop/cpu.shares
echo "512" > /dev/cgroup/cpu/applications/cpu.shares
If you cat those settings after modifying them, they've reverted to their old values (1024, 6144, 2048 respectively).

As for notify on release, those are supposed to clean up old cgroups when the last process in the group dies - probably not that necessary on the n900 as we generally don't have users logging in/out that often.
 

The Following User Says Thank You to thingonaspring For This Useful Post: