From: Jens Axboe <axboe@suse.de>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: "André Tomt" <andre@tomt.net>, "Al Boldi" <a1426z@gawab.com>,
"'Bartlomiej Zolnierkiewicz'" <bzolnier@gmail.com>,
"'Linus Torvalds'" <torvalds@osdl.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] IDE update
Date: Tue, 5 Jul 2005 21:18:42 +0200 [thread overview]
Message-ID: <20050705191840.GC30235@suse.de> (raw)
In-Reply-To: <42CAA075.4040406@rainbow-software.org>
On Tue, Jul 05 2005, Ondrej Zary wrote:
> Jens Axboe wrote:
> >On Tue, Jul 05 2005, Ondrej Zary wrote:
> >
> >>Jens Axboe wrote:
> >>
> >>>On Tue, 2005-07-05 at 15:02 +0200, Ondrej Zary wrote:
> >>>
> >>>
> >>>>>Ok, looks alright for both. Your machine is quite slow, perhaps that is
> >>>>>showing the slower performance. Can you try and make HZ 100 in 2.6 and
> >>>>>test again? 2.6.13-recent has it as a config option, otherwise edit
> >>>>>include/asm/param.h appropriately.
> >>>>>
> >>>>
> >>>>I forgot to write that my 2.6.12 kernel is already compiled with HZ 100
> >>>>(it makes the system more responsive).
> >>>>I've just tried 2.6.8.1 with HZ 1000 and there is no difference in HDD
> >>>>performance comparing to 2.6.12.
> >>>
> >>>
> >>>OK, interesting. You could try and boot with profile=2 and do
> >>>
> >>># readprofile -r
> >>># dd if=/dev/hda of=/dev/null bs=128k
> >>># readprofile > prof_output
> >>>
> >>>for each kernel and post it here, so we can see if anything sticks out.
> >>>
> >>
> >>Here are the profiles (used dd with count=4096) from 2.4.26 and 2.6.12
> >>(nothing from 2.6.8.1 because I don't have the .map file anymore).
> >
> >
> >Looks interesting, 2.6 spends oodles of times copying to user space.
> >Lets check if raw reads perform ok, please try and time this app in 2.4
> >and 2.6 as well.
> >
> ># gcc -Wall -O2 -o oread oread.c
> ># time ./oread /dev/hda
> >
> oread is faster than dd, but still not as fast as 2.4. In 2.6.12, HDD
> led is blinking, in 2.4 it's solid on during the read.
>
> 2.6.12:
> root@pentium:/home/rainbow# time ./oread /dev/hda
>
> real 0m25.082s
> user 0m0.000s
> sys 0m0.680s
>
> 2.4.26:
> root@pentium:/home/rainbow# time ./oread /dev/hda
>
> real 0m23.513s
> user 0m0.000s
> sys 0m2.360s
Hmm, still not as fast, not so good. 2.6 shows more idle time than 2.4,
about 20% more. I seem to remember Ken Chen saying that 2.6 direct io
was still a little slower than 2.4, your really slow hardware could be
showing this to a much greater effect.
I'll try and play with this tomorrow!
--
Jens Axboe
next prev parent reply other threads:[~2005-07-05 19:17 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 16:52 [git patches] IDE update Bartlomiej Zolnierkiewicz
2005-07-04 12:01 ` Al Boldi
2005-07-04 12:30 ` Bartlomiej Zolnierkiewicz
2005-07-04 15:30 ` Al Boldi
2005-07-04 15:41 ` Bartlomiej Zolnierkiewicz
2005-07-04 17:06 ` Al Boldi
2005-07-04 17:38 ` Ondrej Zary
2005-07-04 19:51 ` Bartlomiej Zolnierkiewicz
2005-07-04 20:32 ` Al Boldi
2005-07-04 20:47 ` Bartlomiej Zolnierkiewicz
2005-07-04 23:25 ` André Tomt
2005-07-05 3:43 ` IOWAIT block layer problem Al Boldi
2005-07-05 10:01 ` [git patches] IDE update Ondrej Zary
2005-07-05 10:14 ` Jens Axboe
2005-07-05 10:19 ` Ondrej Zary
2005-07-05 10:42 ` Jens Axboe
2005-07-05 12:35 ` Ondrej Zary
2005-07-05 12:51 ` Jens Axboe
2005-07-05 13:02 ` Ondrej Zary
2005-07-05 13:11 ` Jens Axboe
2005-07-05 15:51 ` Ondrej Zary
2005-07-05 14:21 ` Jens Axboe
2005-07-05 15:00 ` Ondrej Zary
2005-07-05 19:18 ` Jens Axboe [this message]
2005-07-05 19:25 ` Jens Axboe
2005-07-05 21:36 ` Ondrej Zary
2005-07-05 17:27 ` Linus Torvalds
2005-07-05 19:14 ` Jens Axboe
2005-07-05 21:39 ` Ondrej Zary
2005-07-11 14:21 ` Alan Cox
2005-07-06 0:35 ` Grant Coady
2005-07-06 0:51 ` Linus Torvalds
2005-07-06 3:26 ` Al Boldi
2005-07-06 4:56 ` Grant Coady
2005-07-06 5:22 ` Linus Torvalds
2005-07-08 8:48 ` Jens Axboe
2005-07-08 10:20 ` Ingo Molnar
2005-07-08 11:45 ` Jens Axboe
2005-07-07 22:32 ` Mark Lord
2005-07-08 0:06 ` Grant Coady
2005-07-08 11:37 ` Erik Slagter
2005-07-06 20:56 ` Bill Davidsen
2005-07-07 13:47 ` Ondrej Zary
2005-07-07 13:48 ` Bartlomiej Zolnierkiewicz
2005-07-07 19:34 ` Bill Davidsen
2005-07-05 2:47 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 21:37 [git patches] ide update Bartlomiej Zolnierkiewicz
2005-08-18 22:15 ` Linus Torvalds
2005-08-18 22:19 ` Nish Aravamudan
2005-08-19 0:44 ` Mark Lord
2005-08-18 23:08 ` Alan Cox
2005-08-19 9:02 ` Bartlomiej Zolnierkiewicz
2005-08-19 18:06 ` Alan Cox
2005-08-19 23:51 ` Bartlomiej Zolnierkiewicz
2005-08-19 23:52 ` Bartlomiej Zolnierkiewicz
2005-11-10 1:00 Bartlomiej Zolnierkiewicz
2005-11-18 23:21 Bartlomiej Zolnierkiewicz
2005-11-19 23:46 Bartlomiej Zolnierkiewicz
2005-12-15 2:03 Bartlomiej Zolnierkiewicz
2007-05-09 22:46 [git patches] IDE update Bartlomiej Zolnierkiewicz
2007-05-09 22:46 ` Jeff Garzik
2007-05-09 23:20 ` David Miller
2007-05-09 23:23 ` Bartlomiej Zolnierkiewicz
2007-05-09 23:18 ` Jeff Garzik
2007-05-09 22:47 ` Jeff Garzik
2007-05-09 22:59 ` Andrew Morton
2007-05-09 23:15 ` Jeff Garzik
2007-07-09 21:46 Bartlomiej Zolnierkiewicz
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=20050705191840.GC30235@suse.de \
--to=axboe@suse.de \
--cc=a1426z@gawab.com \
--cc=andre@tomt.net \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=torvalds@osdl.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).