News for hackers. Stuff that matters.
Re:How Con Kolivas's BFS CPU scheduler works by ars on Friday October 16, 2009 @05:14PM (#886185)
I have to say it looks really really good. It's tuned specifically for desktop needs.

What are the chances of this getting into mainline? Yes, I read about his history. Maybe it will go in anyway. (But it really needs a new name - any suggestions for a better back-ronym?)

One thing I did not see that it has, is hyperthreading support, i.e. detecting that two cores are really the same, and not scheduling two tasks on the same core, while other are available. And also, not scheduling idle priority tasks on a core used by other tasks.

I emailed him to ask.

Re:How Con Kolivas's BFS CPU scheduler works by ars on Friday October 16, 2009 @05:48PM (#886251)
He replied:

> Does BFS support hyperthreading?

> Meaning, detecting that two cores are really the same, and not scheduling two tasks on the same core, while others are available.

The answer to that is "somewhat". It depends on the topology and workload, but it does not do anything like the complex balancing the mainline scheduler does to achieve this. I don't have enough hardware to see how it works in the real world on different topology and what workloads and how that compares to mainline.

> And also, not scheduling idle priority tasks on a core used by other tasks.

It does nothing smart to separate idle priority tasks from normal ones on SMT siblings vs cores.

And to answer the obvious question that follows these, I don't anticipate I'll be adding any more complex HT management than is already there as that will sway from the philosophy of BFS.

Regards, Con

Re:How Con Kolivas's BFS CPU scheduler works by jrockway on Friday October 16, 2009 @05:21PM (#886204)
Do desktop workloads benefit from hyperthreading? If not, there is no need to clutter this code with support for it.
Re:How Con Kolivas's BFS CPU scheduler works by wmf on Friday October 16, 2009 @05:28PM (#886209)
New Intel desktop/laptop systems have hyperthreading on by default, so the real question is whether desktop workloads are hurt by HT. In that case BFS could improve performance by avoiding co-scheduling (which it currently doesn't appear to do).
Re:How Con Kolivas's BFS CPU scheduler works by jrockway on Friday October 16, 2009 @06:07PM (#886279)
It is disabled by default on every Intel system I own.

But anyway, if people are using unstable Linux scheduling algorithms, I bet they are OK tweaking their BIOS settings, too.

Re:How Con Kolivas's BFS CPU scheduler works by altie on Friday October 16, 2009 @08:23PM (#886425)
There isn't one answer for either desktop or server workloads, only trends. Some processor resources get cut in half between threads, some are duplicated and the threads compete for some others. If your favorite benchmark bottlenecks on a resource that's shared or divided between threads, it'll probably do worse with hyperthreading on; if that's not the case, and a lot of the instructions in the hot path can go to any decoder or ALU, it'll probably do better.