From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Oliver.Korpilla@gmx.de" <Oliver.Korpilla@gmx.de>
Cc: kiu <kiu@gmx.net>, linux-ide@vger.kernel.org
Subject: Re: kernel history of ide performance
Date: Tue, 5 Apr 2005 11:14:39 +0200 [thread overview]
Message-ID: <58cb370e050405021470f3a851@mail.gmail.com> (raw)
In-Reply-To: <4252541B.3030209@gmx.de>
On Apr 5, 2005 11:02 AM, Oliver.Korpilla@gmx.de <Oliver.Korpilla@gmx.de> wrote:
> kiu wrote:
> > Hi ide team,
> >
> > i often heard "uh, since kernel 2.6.bla the ide perfomance is soo bad".
> > Because of that (and the joy of writing bash scripts noone else will understand
> > *g*) i wrote an automated test script to get comparable measurements.
> >
> > The script compiles 2.6.0-2.6.11.6 (yes "" | make oldconfig), boots each kernel,
> > runs hdparm/bonnie++ and create some pngs with gnuplot.
> >
> > I ran the script on a Intel 82371AB/EB/MB PIIX4/PIICeleron 333/IC35L040AVER07
> > machine and you can find the results here:
> >
> > http://www.kiu.weite-welt.com/misc/idetest
> >
> > I am quite busy at the moment and hopefully have time next month to clean up the
> > scripts for a release (are you interested?) and do further testing...
>
> This looks like a mixed bag: some regression, some clear improvements,
> mostly the same. Nice work!
>
> Does this portray the IDE situation or more the situation of the PIIX
> chipset - I guess the code isn't changed as much since it should be
> rather mature?
Probably the situation of VM code...
Having scripts at hand would be useful to double check that
testing procedure itself is OK.
Bartlomiej
next prev parent reply other threads:[~2005-04-05 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 8:46 kernel history of ide performance kiu
2005-04-05 9:00 ` Bartlomiej Zolnierkiewicz
2005-04-05 9:02 ` Oliver.Korpilla
2005-04-05 9:14 ` Bartlomiej Zolnierkiewicz [this message]
2005-04-05 9:34 ` kiu
2005-04-13 18:57 ` Mark Lord
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=58cb370e050405021470f3a851@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=Oliver.Korpilla@gmx.de \
--cc=kiu@gmx.net \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).