linux-kernel - Re: Question about fair schedulers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200706231001.02497.info@gnebu.es>
Date:	Sat, 23 Jun 2007 10:01:02 +0200
From:	Alberto Gonzalez <info@...bu.es>
To:	Paolo Ornati <ornati@...twebnet.it>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Question about fair schedulers

Thanks for your thoughts.

On Saturday 23 June 2007, Paolo Ornati wrote:
> On Sat, 23 Jun 2007 00:07:15 +0200
>
> Alberto Gonzalez wrote:
> > My conclusion is that SD behaves as expected: it's more fair. But for a
> > desktop, shouldn't an "intelligently unfair" scheduler be better?
>
> "intelligently unfair" is what the current scheduler is (because of
> interactivity estimator).
>
> When it works (say 90% of the time) the desktop feels really good...
> but when it doesn't it can be a disaster.

I see. So you mean that in 90% of the cases the mainline scheduler behaves 
better than fair schedulers, but when its "logic" fails it behaves much worse 
(the other 10% cases)? In my very simple test scenario the mainline scheduler 
did behave much better. Maybe the problem comes with very complex scenarios 
like the ones I've seen when testing these 2 fair schedulers (something like 
compiling a kernel while you open 5 instances of glxgears, write an email, 
play music in Amarok and watch 2 HD videos all at the same time). The 
question would then be if these kind of situations are likely to happen in 
real world, or even if it doesn't make more sense to try to improve the logic 
of the mainline scheduler so that those 10% cases are handled better instead 
of writing a new one that would behave worse in 90% of the cases and better 
in the other 10%.

	Alberto.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/