If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
No announcement yet.
Con Kolivas is working on a new scheduler for Desktop/Multimedia/Gaming PCs
I posted proof on lkml. See the latencytop and tracing results. Also, with so many people confirming, this must be a cabal/conspiracy to destroy the mainline scheduler, right? :P
Heh, this is what I thought (don't forget some note in wikipedia ;p).
Seriously. Con's code helps *immensely* not only here, but elsewhere too (the Android guys are having multiple orgasms already, and obviously they're not using Gentoo.)
Let's hope devs will do everything to make things better. I just don't like when people base their opinions on something weak (I'm not according to you). P.S. mentioning Gentoo I thought only about custom configs, I'm not saying there's something wrong with it.
i would like to point out that ingo's test hardware puts it at the highest point Con said he thought it would scale too.... a 16 thread machine...
this is meant as a *desktop* scheduler, a dual quad core hyper-threading system is not exactly a typical desktop PC.
There's no doubt CFS beats BFS in performance (shouldn't bfs be better from beginning and then just drastically choke when more cores are involved? I do not know, but maybe all cores were used from begining hmm...), but what counts the most on desktops is responsiveness and this is what someone should measure.
Ingo may not have meant it like this, but using such hardware really felt like a deliberate attempt to disprove Con's scheduler.
I'm on the fence about this issue, since I haven't really felt any issues with the current scheduler, but if the improvements on single-, dual-, tri- and quad-core systems are repeatable (you know, the hardware desktop PCs actually *have*), then we might have something good on our hands.
The issue is that kernel devs are (rightly) extremely resistant to change on this area. However, if this shows so significant improvements that Android and other distros adapt it (despite being an out of tree patch), we will likely see one of two things:
1. This makes it into the kernel. (Patch from Con? Yeah, right...)
2. CFS is improved to match BFS on the desktop.