linux-kernel - Re: about modularization

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] [day] [month] [year] [list]

Date:	Fri, 3 Aug 2007 17:13:33 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"T. J. Brumfield" <enderandrew@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: about modularization

* T. J. Brumfield <enderandrew@...il.com> wrote:

> CFS is apparently better in its simplicity, however others are 
> reporting that SD still provides benefits for 3D gaming. [...]

even for 3D gaming the opposite of what you say seems to be the case:

  http://people.redhat.com/mingo/misc/cfs-sd-ut2004-perf.jpg
  http://people.redhat.com/mingo/misc/cfs-vs-sd-wine-quake.jpg

  ( more such measurements were done and reported, i stopped doing
    graphs after the first two. )

but in any case, the main "target" of CFS was not even SD (although it 
is certainly desirable to handle any load at least as well as SD) but 
the _mainline_ scheduler. SD was the primary selection of a relatively 
small subset of existing Linux users, and SD had known (and intentional) 
tradeoffs over the mainline scheduler in certain areas. CFS tried to do 
zero tradeoffs over the existing scheduler, to not introduce regressions 
to the many users who found the existing scheduler just good enough. 
That's been a success so far, at the moment there's no open CFS 
"interactivity regression" relative to the 2.6.22 mainline scheduler.

	Ingo
-
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/