From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Bill Davidsen <davidsen@tmr.com>
Cc: chriswhite@gentoo.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Quick update on latest Linux kernel performance
Date: Thu, 15 Sep 2005 09:15:03 +0200 [thread overview]
Message-ID: <43291F77.6000505@aitel.hist.no> (raw)
In-Reply-To: <43284B61.50509@tmr.com>
Bill Davidsen wrote:
> Chris White wrote:
[...]
>>
>> The benchmarks here have a slight flaw in that the main hardware
>> components tested are not given. About the only thing I can see
>> regarding these tests is what processor they run on. Displaying
>> network performance tests without showing the network card or io
>> tests without showing the disk controller seems rather odd. I guess
>> it comes down to requesting a full hardware rundown. If this is
>> displayed someplace on the site or elsewhere please provide the link.
>
>
> Unless the hardware was changed, this is not particularly relevant.
> It's good testing to change only one thing, so you know that's what
> caused the change in results.
The benchmarks surely says something about the kernel regardless of
wether they specify hardware. But if you want performance regressions
fixed, then the hardware list is necessary. It is interesting to know
wether the test machine used SCSI or IDE for IO for example, for those
systems get different patches. One may regress while another improves.
Similiar for all the different network adapter drivers and so on.
Helge Hafting
next prev parent reply other threads:[~2005-09-15 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 21:32 Quick update on latest Linux kernel performance Chen, Kenneth W
2005-09-14 6:17 ` Chris White
2005-09-14 16:10 ` Bill Davidsen
2005-09-15 7:15 ` Helge Hafting [this message]
2005-09-20 14:12 ` Danial Thom
-- strict thread matches above, loose matches on Subject: below --
2005-09-15 17:39 Felix Oxley
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=43291F77.6000505@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=chriswhite@gentoo.org \
--cc=davidsen@tmr.com \
--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