On Thu, 3 Mar 2011 16:19:07 +0200 "Kirill A. Shutsemov" <kirill@xxxxxxxxxxxxx> wrote: > --- /dev/null > +++ b/Documentation/cgroups/timer_slack.txt > @@ -0,0 +1,64 @@ > +Timer Slack Controller > +===================== > + > +Overview > +-------- > + > +Every task_struct has timer_slack_ns value. This value uses to round up > +poll() and select() timeout values. This feature can be useful in > +mobile environment where combined wakeups are desired. > + > +cgroup subsys "timer_slack" implements timer slack controller. It > +provides a way to set minimal timer slack value for a group of tasks. > +If a task belongs to a cgroup with minimal timer slack value higher than > +task's value, cgroup's value will be applied. All I'm seeing here is a bunch of code, but no reason has been provided for merging any of it. Why do we need a cgroup for this as opposed to (say) inheritance over fork(), or a system-wide knob, or a per-process/threadgroup knob, or just leaving the existing code as-is? Presumably you felt that a cgroup approach is better for manageability, but you didn't tell us about this and you didn't explore alternative ways of solving the problem-which-you-didn't-describe. Carefully describing the proposed feature and the overall value which it brings does help to grease the wheels and is worth spending some time over, please. Don't expect the entire audience to be mind-readers! -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
