From: Jens Axboe <axboe@suse.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Robert Love <rml@tech9.net>,
Andre Hedrick <andre@linuxdiskcert.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] 2.5.3-pre1 ata-253p1-2
Date: Fri, 18 Jan 2002 08:58:50 +0100 [thread overview]
Message-ID: <20020118085850.L27835@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10201171455360.344-100000@master.linux-ide.org> <Pine.LNX.4.10.10201171455360.344-100000@master.linux-ide.org> <5.1.0.14.2.20020118004455.00b07800@pop.cus.cam.ac.uk>
In-Reply-To: <5.1.0.14.2.20020118004455.00b07800@pop.cus.cam.ac.uk>
On Fri, Jan 18 2002, Anton Altaparmakov wrote:
> >> You have to give Jens the credit for gluing it togather, because there
> >was
> >> no way I would have figured out the suttle issues of BIO. There are
> >> serveral additions need to fix all the archs so hope to have something
> >> today.
> >
> >Well, good work to both of you. It is an excellent driver. Please
> >submit it for pre2.
>
> I second that. 2.5.3-pre1 + 2nd patch from Jens + daft compile fixes is
> running fine on my Athlon/VIA chipset both UDMA100 and PIO4 on my 60GXP
> drive! Brilliant work guys!
Thanks!
> There is only one odd thing and that is that PIO transfers are slower in
> 2.5.3-pre1 + 2nd patch from Jens + daft compile fixes compared to in
> 2.5.2-pre11-vanilla.
>
> PIO mode, hdparm -t /dev/hda:
>
> on 2.5.3-pre1 + 2nd Jens patch: 4.62MB/s
> on 2.5.2-pre11 vanilla: 7.36MB/s
>
> DMA transfers are the same with both kernels, peaking at 38-39MB/s which is
> I believe the theoretical upper limit for the 60GXP so there was not much
> room for visible improvement (2.5.3-pre1 is slightly faster in that it gave
> in three tests 38.79MB/s while 2.5.2-pre11 gave in three tests 38.32MB/s,
> so if you believe those ACB is .4 MB/s faster).
>
> I don't care that PIO has become slower, all modern devices are happy with
> UDMA, and so am I. (-: But I thought I should mention it.
Interesting, I dunno where this performance decrease comes from right
now. But I'm sure we can make it go at least as fast as 2.5.2-pre11, the
primary concern right now was solid PIO + mult mode again, and I think
we've achieved that.
> Note that 2.5.3-pre1 now survives find . -type f -exec md5sum "{}" \; both
> in PIO and UDMA mode so it can really be considered stable on UP system.
Great, thanks for testing.
--
Jens Axboe
prev parent reply other threads:[~2002-01-18 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 13:46 [patch] 2.5.3-pre1 ide updates Jens Axboe
2002-01-17 14:29 ` Anton Altaparmakov
2002-01-17 14:28 ` Jens Axboe
2002-01-17 14:29 ` Jens Axboe
2002-01-17 14:34 ` [PATCH] 2.5.3-pre1 ata-253p1-2 Jens Axboe
2002-01-17 22:16 ` Robert Love
2002-01-17 22:59 ` Andre Hedrick
2002-01-17 23:13 ` Robert Love
2002-01-18 1:00 ` Anton Altaparmakov
2002-01-18 7:58 ` Jens Axboe [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=20020118085850.L27835@suse.de \
--to=axboe@suse.de \
--cc=aia21@cam.ac.uk \
--cc=andre@linuxdiskcert.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.com \
/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