From: Kevin Puetz <puetzk@iastate.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: as vs cfq vs deadline
Date: Tue, 25 Feb 2003 16:42:32 -0600 [thread overview]
Message-ID: <b3grga$7oh$1@main.gmane.org> (raw)
In-Reply-To: 20030223164924.16952.qmail@linuxmail.org
Paolo Ciarrocchi wrote:
> Hi all,
> I've run a 'let's check if it does not skip frames test'.
> kernel is 2.5.62-mm2.
>
> ** How I performed the test **
> startx
> I've opened to xterminal
>
> terminal1
> [test@frodo test]$ glxgears
>
> terminal2
> ./dbench 16
>
> Following the results:
>
<snip>
> I can not see any difference in the results above.
>
> I guess the test I've run it is not a good test, isn't it ?
a) you're only looking at glxgears average framerate, so you've not measured
whether it drops frames at all, and
b) glxgears does no disk i/o at all, so it shouldn't care a bit what the I/O
scheduelr is doing (other than how much cpu the kernel is using, which
shouldn't be all that high)
> Comments/suggesiontions ?
>
> Ciao,
> Paolo
>
prev parent reply other threads:[~2003-02-25 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 16:49 as vs cfq vs deadline Paolo Ciarrocchi
2003-02-25 22:42 ` Kevin Puetz [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='b3grga$7oh$1@main.gmane.org' \
--to=puetzk@iastate.edu \
--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