From: Tomas Szepe <szepe@pinerecords.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Dennis Grant <trog@wincom.net>, linux-kernel@vger.kernel.org
Subject: Re: Identifying/activating faster ATAxx modes (WAS kernel config tale of woe)
Date: Tue, 26 Nov 2002 13:15:45 +0100 [thread overview]
Message-ID: <20021126121545.GL29196@louise.pinerecords.com> (raw)
In-Reply-To: <20021126121329.GI24796@fs.tum.de>
> > > /dev/hda:
> > >
> > > Model=Maxtor 6E030L0, FwRev=NAR61590, SerialNo=E106SZLE
> > > Config={ Fixed }
> > > RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
> > > BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
> > > CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=60058656
> > > IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> > > PIO modes: pio0 pio1 pio2 pio3 pio4
> > > DMA modes: mdma0 mdma1 mdma2
> > > UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> >...
> > This is weird. Your disk seems to be set up for udma6 (UATA133),
> > which should provide for transfer rates of at least 40MiB/s.
> >...
>
> The information in "hdparm -i" shows the identification info of the
> drive. It doesn't show whether DMA is actually used (you need
> "hdparm -v" for this)...
While this is true, I fail to see why the -i output would report
udma6 as being the current transfer mode instead of a pio one if
DMA were disabled.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2002-11-26 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 3:31 Dennis Grant
2002-11-26 3:49 ` Tomas Szepe
2002-11-26 12:13 ` Adrian Bunk
2002-11-26 12:15 ` Tomas Szepe [this message]
2002-11-26 12:48 ` Adrian Bunk
2002-11-26 13:05 ` Tomas Szepe
2002-11-26 12:44 ` Adrian Bunk
2002-11-26 12:53 ` Adrian Bunk
2002-11-26 10:53 Christian Guggenberger
2002-11-26 13:36 Dennis Grant
2002-11-26 13:42 Dennis Grant
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=20021126121545.GL29196@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trog@wincom.net \
/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
all inboxes | Powered by JetHome®