From: Nick Piggin <piggin@cyberone.com.au>
To: rwhron@earthlink.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] 2.5.68 and 2.5.68-mm2
Date: Fri, 02 May 2003 04:10:54 +1000 [thread overview]
Message-ID: <3EB1632E.5000302@cyberone.com.au> (raw)
In-Reply-To: <20030430005902.GA32599@rushmore>
rwhron@earthlink.net wrote:
>>A run with deadline on mm would be nice to see.
>>
>
>Summary:
>Most benchmarks don't show much difference between 2.5.68-mm2 using
>anticipatory vs deadline scheduler. AIM7 had almost no difference.
>Tiobench has the most difference.
>
OK, thanks for that. I'd say it could be a TCQ or possibly
RAID or driver problem. I don't have anything in mind to
fix it yet but it has to be addressed at some point.
next prev parent reply other threads:[~2003-05-01 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 0:59 [BENCHMARK] 2.5.68 and 2.5.68-mm2 rwhron
2003-05-01 18:10 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-28 21:58 rwhron
2003-04-26 1:58 rwhron
2003-04-26 2:20 ` Nick Piggin
2003-04-26 3:11 ` Nick Piggin
2003-04-25 23:09 rwhron
2003-04-25 23:25 ` Andrew Morton
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=3EB1632E.5000302@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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