From: Ingo Molnar <mingo@elte.hu>
To: Andr? Goddard Rosa <andre.goddard@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: sched-devel feedback
Date: Thu, 27 Sep 2007 08:54:47 +0200 [thread overview]
Message-ID: <20070927065447.GA28697@elte.hu> (raw)
In-Reply-To: <b8bf37780709261828m6f9f7318qe753d8b32055bf@mail.gmail.com>
* Andr? Goddard Rosa <andre.goddard@gmail.com> wrote:
> Hi, Ingo , Mike and Peter!
>
> Just passing around to say that 2.6.23-rc8-sched-dev is the best
> scheduler ever to me. It's great for 3D games.
cool! :-)
> http://www.openarena.ws/?files is really great with this
> scheduler. I played a whole match without no slowdown, smooth playing
> all the time. I had never played it before like this, it made a huge
> difference to me. Even older CFS releases and -ck did not made it
> sooooo smooth. It was really smooth _all_ the time.
i'm wondering, in previous schedulers, under what situations did you
notice smoothness problems? Was the scenario in any way deterministic,
or just random delays that are hard to describe?
Just in case you have smoothness problems in the future, a good way of
measuring it objectively is to enable CONFIG_SCHED_DEBUG=y and
CONFIG_SCHEDSTATS=y and to monitor the se.wait_max field in the
/proc/PID/tasks/*/sched file[s].
Every time there's some ruckle or other smoothness problem, that field's
value should increase. (a few milliseconds up to a few dozen
milliseconds is fine normally - anything above 100 msecs is probably
less fine.) By looking at that latency field you can compare two
kernels. (And by echoing 0 to the sched file you can clear these stats.)
So by saying "under .23-rc8 se.wait_max was 50 msecs while in .24-rc1 it
increased to 250 msecs" everyone can effectively complain to us about
smoothness problems :-)
> The scheduler team did a really good work on this!
>
> Thank you so much for this great work,
you are welcome!
Ingo
prev parent reply other threads:[~2007-09-27 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 1:28 sched-devel feedback André Goddard Rosa
2007-09-27 6:54 ` Ingo Molnar [this message]
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=20070927065447.GA28697@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=andre.goddard@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox