From: Vojtech Pavlik <vojtech@suse.cz>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [preview] Latest AMD & VIA IDE drivers with UDMA100 support
Date: Sun, 21 Jan 2001 12:44:52 +0100 [thread overview]
Message-ID: <20010121124452.B804@suse.cz> (raw)
In-Reply-To: <cv8k6ts9oeb72pmhh9hsfjta6uen511a0j@4ax.com> <Pine.LNX.4.10.10101202015510.1776-100000@coffee.psychology.mcmaster.ca> <neel6tgsvv861oon326ggetmf82v1inu1v@4ax.com>
In-Reply-To: <neel6tgsvv861oon326ggetmf82v1inu1v@4ax.com>; from alan@chandlerfamily.org.uk on Sun, Jan 21, 2001 at 10:51:12AM +0000
On Sun, Jan 21, 2001 at 10:51:12AM +0000, Alan Chandler wrote:
> On Sat, 20 Jan 2001 20:18:34 -0500 (EST), you wrote:
>
>
> >that's not the topic: Andre's talking about pci-clock-based timing
> >constants the the driver programs into the ide controller - a matter
> >of an extra few/more nanoseconds.
>
> I know, but when looking hard for a problem in one place and not
> finding it, it is sometimes helpful to consider other options.
>
> I am getting errors under 2.4.0 which didn't appear in 2.2.17 - and as
> far as I could see from hdparm - both were at UDMA mode 2 (I assume
> thats what the * means - the man page wasn't very clear). My drives
> only handle up to this mode, and I was wondering if the new driver was
> trying to run them at a mode higher than they were supposed to go.
>
> This massive difference in timing seemed significant.
No, but to me it seems that even though UDMA2 mode is selected in the
drive in 2.2.17 (that's what the * means), the kernel doesn't use DMA,
and thus everything works in PIO4. This would well explain the speed
difference.
> >quite slow in either case, at least for modern hardware (which is
> >all in the 20-40 MB/s range). this looks like a PIO vs DMA difference
> >to me, not even UDMA. of course, hdparm can tell you what mode you're in.
>
> I did discover a difference - 2.2.17 set the drives with multisector
> off, 2.4.0 was setting multisector on.
Multisector is valid only in PIO modes. If both were doing some kind of
DMA, it wouldn't change anything.
> However, I have redone the
> timing with multisector turned on in the 2.2.17 case and the
> difference is still there.
>
> Under 2.2.17 with multisector turned on
>
>
> /dev/hda:
>
> Model=IBM-DHEA-38451, FwRev=HP8OA20C, SerialNo=SH0SH0X1795
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=28
> BuffType=3(DualPortCache), BuffSize=472kB, MaxMultSect=16,
> MultSect=16
> DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=16514064
> tDMA={min:120,rec:120}, DMA modes: sword0 sword1 sword2 mword0 mword1
> mword2
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
> UDMA modes: mode0 mode1 *mode2
>
> ------------------
>
> /dev/hda:
> Timing buffered disk reads: 64 MB in 19.88 seconds = 3.22 MB/sec
>
>
> Under 2.4.0
>
>
> /dev/hda:
>
> Model=IBM-DHEA-38451, FwRev=HP8OA20C, SerialNo=SH0SH0X1795
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=28
> BuffType=3(DualPortCache), BuffSize=472kB, MaxMultSect=16,
> MultSect=16
> DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=16514064
> tDMA={min:120,rec:120}, DMA modes: sword0 sword1 sword2 mword0 mword1
> mword2
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
> UDMA modes: mode0 mode1 *mode2
>
> ------------------
>
> /dev/hda:
> Timing buffered disk reads: 64 MB in 6.58 seconds = 9.73 MB/sec
>
>
>
> I don't suppose the fact that my hdparm is oldish (3.6 I think) have
> any bearing on this?
No, 3.6 is OK I think.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-21 12:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 17:14 [preview] Latest AMD & VIA IDE drivers with UDMA100 support Alan Chandler
[not found] ` <Pine.LNX.4.10.11101200938180.2302-100000@master.linux-ide.org>
2001-01-20 18:45 ` Alan Chandler
2001-01-20 20:56 ` Vojtech Pavlik
2001-01-20 22:57 ` Andre Hedrick
2001-01-20 23:55 ` Alan Chandler
[not found] ` <Pine.LNX.4.10.10101202015510.1776-100000@coffee.psychology.mcmaster.ca>
2001-01-21 10:51 ` Alan Chandler
2001-01-21 11:44 ` Vojtech Pavlik [this message]
2001-01-21 9:46 ` Vojtech Pavlik
2001-01-21 13:04 ` Jan Niehusmann
[not found] ` <Pine.Linu.4.10.10101211237230.2017-100000@mikeg.weiden.de>
2001-01-21 16:32 ` Vojtech Pavlik
2001-01-21 20:49 ` Andre Hedrick
2001-01-22 0:12 ` Dan Hopper
2001-01-22 6:06 ` Mike Galbraith
2001-01-25 21:54 ` David D.W. Downey
2001-01-25 21:56 ` Vojtech Pavlik
2001-01-25 22:00 ` Andre Hedrick
2001-01-26 0:26 ` David D.W. Downey
2001-01-24 18:04 ` Andre Hedrick
2001-01-24 19:25 ` Vojtech Pavlik
2001-01-24 21:58 ` Andre Hedrick
2001-01-25 12:20 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2001-01-19 15:56 Vojtech Pavlik
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=20010121124452.B804@suse.cz \
--to=vojtech@suse.cz \
--cc=alan@chandlerfamily.org.uk \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.