|| ||Con Kolivas <kernel-AT-kolivas.org> |
|| ||Ingo Molnar <mingo-AT-elte.hu> |
|| ||Re: BFS vs. mainline scheduler benchmarks and measurements |
|| ||Mon, 7 Sep 2009 13:50:16 +1000|
Peter Zijlstra <a.p.zijlstra-AT-chello.nl>,
Mike Galbraith <efault-AT-gmx.de>|
|| ||Article, Thread
2009/9/7 Ingo Molnar <email@example.com>:
> hi Con,
Well hello there.
> I've read your BFS announcement/FAQ with great interest:
> Â Â http://ck.kolivas.org/patches/bfs/bfs-faq.txt
> I understand that BFS is still early code and that you are not
> targeting BFS for mainline inclusion - but BFS is an interesting
> and bold new approach, cutting a _lot_ of code out of
> kernel/sched*.c, so it raised my curiosity and interest :-)
Hard to keep a project under wraps and get an audience at the same
time, it is. I do realise it was inevitable LKML would invade my
personal space no matter how much I didn't want it to, but it would be
rude of me to not respond.
> In the announcement and on your webpage you have compared BFS to
> the mainline scheduler in various workloads - showing various
> improvements over it. I have tried and tested BFS and ran a set of
> benchmarks - this mail contains the results and my (quick)
/me sees Ingo run off to find the right combination of hardware and
benchmark to prove his point.
[snip lots of bullshit meaningless benchmarks showing how great cfs is
and/or how bad bfs is, along with telling people they should use these
artificial benchmarks to determine how good it is, demonstrating yet
again why benchmarks fail the desktop]
I'm not interested in a long protracted discussion about this since
I'm too busy to live linux the way full time developers do, so I'll
keep it short, and perhaps you'll understand my intent better if the
FAQ wasn't clear enough.
Do you know what a normal desktop PC looks like? No, a more realistic
question based on what you chose to benchmark to prove your point
would be: Do you know what normal people actually do on them?
Feel free to treat the question as rhetorical.
/me checks on his distributed computing client's progress, fires up
his next H264 encode, changes music tracks and prepares to have his
arse whooped on quakelive.
to post comments)