From: William Lee Irwin III <wli@holomorphy.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Bill Davidsen <davidsen@tmr.com>,
Miguel Figueiredo <elmig@debianpt.org>,
Ray Lee <ray-lk@madrabbit.org>,
Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: Sched - graphic smoothness under load - cfs-v13 sd-0.48
Date: Tue, 22 May 2007 21:06:50 -0700 [thread overview]
Message-ID: <20070523040650.GS19966@holomorphy.com> (raw)
In-Reply-To: <200705241036.45179.kernel@kolivas.org>
On Wednesday 23 May 2007 10:28, Bill Davidsen wrote:
>>> kernel 2.6.21-cfs-v13 2.6.21-ck2
>>> a) 194464 254669
>>> b) 54159 124
>> Everyone seems to like ck2, this makes it look as if the video display
>> would be really pretty unusable. While sd-0.48 does show an occasional
>> video glitch when watching video under heavy load, it's annoying rather
>> than unusable.
On Thu, May 24, 2007 at 10:36:44AM +1000, Con Kolivas wrote:
> That's because the whole premise of your benchmark relies on a workload that
> yield()s itself to the eyeballs on most graphic card combinations when using
> glxgears. Your test remains a test of sched_yield in the presence of your
> workloads rather than anything else. If people like ck2 it's because in the
> real world with real workloads it is better, rather than on a yield() based
> benchmark. Repeatedly the reports are that 3d apps and games in normal usage
> under -ck are better than mainline and cfs.
Maybe people should explicitly hack on sched_yield() for these things
and do comparative benchmarking of sched_yield() implementations.
-- wli
next prev parent reply other threads:[~2007-05-23 4:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 20:02 Sched - graphic smoothness under load - cfs-v13 sd-0.48 Bill Davidsen
2007-05-19 20:22 ` Ray Lee
2007-05-20 0:44 ` Bill Davidsen
2007-05-20 6:12 ` Michael Gerdau
2007-05-20 6:30 ` Ray Lee
2007-05-20 6:59 ` Michael Gerdau
2007-05-20 7:20 ` Ray Lee
2007-05-20 6:55 ` Ray Lee
2007-05-21 18:27 ` Matt Keenan
2007-05-19 20:36 ` Diego Calleja
2007-05-19 20:55 ` Ray Lee
2007-05-19 23:21 ` Mike Galbraith
2007-05-20 16:29 ` Miguel Figueiredo
2007-05-20 16:44 ` Ray Lee
2007-05-20 16:58 ` Miguel Figueiredo
2007-05-20 17:19 ` Ray Lee
2007-05-22 17:55 ` Bill Davidsen
2007-05-22 20:01 ` Miguel Figueiredo
2007-05-23 0:28 ` Bill Davidsen
2007-05-23 13:10 ` Bill Davidsen
2007-05-23 18:29 ` Miguel Figueiredo
2007-05-23 20:45 ` Bill Davidsen
2007-05-23 21:03 ` Miguel Figueiredo
2007-05-24 0:36 ` Con Kolivas
2007-05-23 4:06 ` William Lee Irwin III [this message]
2007-05-23 5:23 ` Michael Gerdau
2007-05-23 7:58 ` Xavier Bestel
2007-05-23 8:21 ` Bill Huey
2007-05-23 18:22 ` Ian Romanick
2007-05-23 18:43 ` Xavier Bestel
2007-05-23 17:22 ` Bill Davidsen
2007-05-23 16:59 ` Bill Davidsen
2007-05-22 17:22 ` Bill Davidsen
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=20070523040650.GS19966@holomorphy.com \
--to=wli@holomorphy.com \
--cc=davidsen@tmr.com \
--cc=elmig@debianpt.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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