From: Mike Galbraith <efault@gmx.de>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Andres Freund <andres@anarazel.de>,
Con Kolivas <kernel@kolivas.org>,
Jason Garrett-Glaser <darkshikari@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML Mailinglist <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: x264 benchmarks BFS vs CFS
Date: Sun, 20 Dec 2009 16:13:01 +0100 [thread overview]
Message-ID: <1261321981.6105.60.camel@marge.simson.net> (raw)
In-Reply-To: <1261311050.14314.67.camel@localhost>
On Sun, 2009-12-20 at 13:10 +0100, Kasper Sandberg wrote:
> and as for CFS, it SHOULD exhibit fair behavior anyway, isnt it called
> "completely FAIR scheduler" ? or is that just the marketing name?
Clue: CFS _did_ distribute CPU evenly. Ponder that for a moment.
-Mike
next prev parent reply other threads:[~2009-12-20 15:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 9:33 x264 benchmarks BFS vs CFS Kasper Sandberg
2009-12-17 10:42 ` Jason Garrett-Glaser
2009-12-17 10:53 ` Ingo Molnar
2009-12-17 11:00 ` Kasper Sandberg
2009-12-17 12:08 ` Ingo Molnar
2009-12-17 12:35 ` Kasper Sandberg
2009-12-17 15:47 ` Arjan van de Ven
2009-12-17 13:30 ` Mike Galbraith
2009-12-18 10:54 ` Kasper Sandberg
2009-12-18 11:41 ` Mike Galbraith
2009-12-17 21:22 ` Thomas Fjellstrom
2009-12-18 10:56 ` Kasper Sandberg
2009-12-18 1:18 ` Jason Garrett-Glaser
2009-12-18 5:23 ` Ingo Molnar
2009-12-18 7:30 ` Mike Galbraith
2009-12-18 10:11 ` Jason Garrett-Glaser
2009-12-18 12:49 ` Mike Galbraith
2009-12-18 13:06 ` Ingo Molnar
2009-12-18 13:36 ` Mike Galbraith
2009-12-18 13:53 ` Mike Galbraith
2009-12-18 10:57 ` Kasper Sandberg
2009-12-18 11:05 ` Jason Garrett-Glaser
2009-12-19 1:08 ` Con Kolivas
2009-12-19 4:03 ` Mike Galbraith
2009-12-19 17:36 ` Kasper Sandberg
2009-12-19 20:57 ` Mike Galbraith
2009-12-20 3:22 ` Andres Freund
2009-12-20 12:10 ` Kasper Sandberg
2009-12-20 13:09 ` Kasper Sandberg
2009-12-20 15:13 ` Mike Galbraith [this message]
2009-12-20 15:51 ` Mike Galbraith
2009-12-22 7:33 ` Jason Garrett-Glaser
2009-12-22 7:39 ` Jason Garrett-Glaser
2009-12-18 10:56 ` Kasper Sandberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1261321981.6105.60.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=andres@anarazel.de \
--cc=darkshikari@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.