From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Thomas Molina <tmolina@cablespeed.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 performance problems
Date: Tue, 30 Dec 2003 01:43:42 +0200 [thread overview]
Message-ID: <1072741422.25741.67.camel@nosferatu.lan> (raw)
In-Reply-To: <Pine.LNX.4.58.0312291803420.5835@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Tue, 2003-12-30 at 01:05, Thomas Molina wrote:
> Sorry. One other bit of data from 2.6:
>
> [root@lap bitkeeper]# hdparm -i /dev/hda
>
> /dev/hda:
>
> Model=IBM-DJSA-220, FwRev=JS4OAC3A, SerialNo=44V44FT3300
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> BuffType=DualPortCache, BuffSize=1874kB, MaxMultSect=16, MultSect=16
> CurCHS=17475/15/63, CurSects=16513875, LBA=yes, LBAsects=39070080
> IORDY=on/off, tPIO={min:240,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
> AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled
> Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1:
>
> * signifies the current active mode
Any reason it is currently set to udma2 where it support udma4 ?
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-29 23:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 22:07 Thomas Molina
2003-12-29 22:21 ` Linus Torvalds
2003-12-29 22:58 ` Thomas Molina
2003-12-29 23:04 ` Linus Torvalds
2003-12-30 14:14 ` Thomas Molina
2003-12-30 14:39 ` William Lee Irwin III
2003-12-30 21:14 ` Thomas Molina
2003-12-30 21:23 ` Linus Torvalds
2003-12-31 0:50 ` Thomas Molina
2003-12-31 1:01 ` Linus Torvalds
2003-12-31 1:34 ` Andrew Morton
2003-12-31 11:25 ` bert hubert
2003-12-30 21:35 ` William Lee Irwin III
2003-12-30 23:46 ` Roger Luethi
2003-12-30 18:20 ` Linus Torvalds
2003-12-29 23:14 ` Martin Schlemmer
2003-12-30 5:09 ` William Lee Irwin III
2003-12-30 10:27 ` Thomas Molina
2003-12-29 23:25 ` David B. Stevens
2003-12-29 23:05 ` Thomas Molina
2003-12-29 23:43 ` Martin Schlemmer [this message]
2003-12-30 0:17 ` Thomas Molina
2003-12-30 1:23 ` Martin Schlemmer
2003-12-30 1:27 ` Dave Jones
2003-12-30 1:37 ` Martin Schlemmer
2003-12-30 1:40 ` Dave Jones
2003-12-30 1:49 ` Thomas Molina
2003-12-30 2:03 ` Mike Fedyk
2004-01-03 19:37 ` Bill Davidsen
2003-12-30 1:25 ` Roger Luethi
2003-12-30 1:37 ` Thomas Molina
2003-12-30 19:21 ` Andy Isaacson
2003-12-30 19:40 ` William Lee Irwin III
2003-12-30 22:24 ` Roger Luethi
2003-12-31 0:33 ` Thomas Molina
2003-12-31 10:17 ` Roger Luethi
2003-12-31 11:21 ` Jens Axboe
2003-12-31 21:03 ` Roger Luethi
2004-01-01 1:27 ` Thomas Molina
2004-01-01 10:23 ` Roger Luethi
2004-01-01 23:09 ` Roger Luethi
2004-01-02 10:11 ` Jens Axboe
2003-12-30 1:27 ` Thomas Molina
2003-12-30 2:53 ` Thomas Molina
2003-12-30 11:41 Samium Gromoff
2004-01-03 19:54 ` Bill Davidsen
[not found] ` <200312300855.00741.edt@aei.ca>
2004-01-05 12:33 ` Samium Gromoff
2004-01-05 15:09 ` Ed Tomlinson
2004-01-06 2:23 ` David Lang
2004-01-06 14:44 ` Samium Gromoff
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=1072741422.25741.67.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cablespeed.com \
--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
Powered by JetHome