LWN: Comments on "CFS group scheduling" https://lwn.net/Articles/240474/ This is a special feed containing comments posted to the individual LWN article titled "CFS group scheduling". en-us Fri, 05 Sep 2025 17:15:03 +0000 Fri, 05 Sep 2025 17:15:03 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net CFS group scheduling https://lwn.net/Articles/247073/ https://lwn.net/Articles/247073/ kolyshkin <blockquote> This type of scheduling is called "group scheduling"; Linux has never really supported it with any scheduler.</blockquote> <p>Well, whe scheduler we have in <a href="http://openvz.org/">OpenVZ</a> is doing just that. It's a two-level CPU scheduler. On the first level schedules between groups of processes (with each group being a container), taking into account the (relative) priorities for those groups, and the (absolute) limits on the CPU time being used. On the second level, it schedules the process within chosen group.</p> <p>That's indeed nice that such a feature appears in vanilla kernel.</p> Tue, 28 Aug 2007 15:41:18 +0000 Userspace scheduling policy daemon https://lwn.net/Articles/240804/ https://lwn.net/Articles/240804/ TRS-80 The usual way to handle this is child processes get put into the same group as their parent. Obviously you wouldn't want this for all processes, but the daemon could mark things like make and gcc as creating a new sub-hierarchy. Fri, 06 Jul 2007 10:11:46 +0000 CFS group scheduling https://lwn.net/Articles/240699/ https://lwn.net/Articles/240699/ davecb I've been a happy user of this kind of functionality<br> in Solaris 9 and 10 (before that it was pretty primitive).<br> <p> I originally used for production machines, where a<br> guarantee of a certain amount of CPU to a bunch of<br> processes allows for eevrything from consolidation<br> to having the CPU available for root to use to kill <br> a runaway process.<br> <p> However, I now run it on my laptop, and shove<br> background proceses into a different scheduling<br> group so they don't interfere with anything in<br> the foreground. Think of this as bg and nice<br> done right (;-))<br> <p> --dave<br> Thu, 05 Jul 2007 14:35:36 +0000 Userspace scheduling policy daemon https://lwn.net/Articles/240692/ https://lwn.net/Articles/240692/ abatters <font class="QuotedText">&gt; So any particular policy can be implemented through the creation of a simple, user-space daemon which responds to process creation events by placing newly-created processes in the right group.</font><br> <p> Using a userspace daemon to set process scheduling policy might be fine for long-running processes like the X server, but wouldn't it introduce a lot of overhead for short-lived processes like gcc during kernel builds? I expect it would add a few context switches of overhead to every fork(); that doesn't seem consistent with general kernel developer attitude towards efficiency.<br> Thu, 05 Jul 2007 13:49:11 +0000 CFS group scheduling https://lwn.net/Articles/240691/ https://lwn.net/Articles/240691/ mclasen@redhat.com Might be worthwhile to point out that the CFS scheduler has been included in the Fedora devel kernel for a few weeks now. <br> Thu, 05 Jul 2007 13:33:55 +0000