From: Max Payne <"max..payne"@freemail.hu>
To: jfontain@free.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE performance drop between 2.4.23 and 2.6.0
Date: Thu, 25 Dec 2003 17:39:08 +0100 (CET) [thread overview]
Message-ID: <freemail.20031125173908.53283@fm3.freemail.hu> (raw)
Hi!
IO scheduler issue? Please try repeating your tests with
'elevator=deadline' at boot.
2003-12-23, k keltezéssel Jean-Luc Fontaine ezt írta:
> Using hdparm -Tt /dev/hdb:
>
> on 2.4:
> Timing buffer-cache reads: 168 MB in 2.01 seconds =
83.58 MB/sec
> Timing buffered disk reads: 44 MB in 3.12 seconds =
14.10 MB/sec
> on 2.6:
> Timing buffer-cache reads: 172 MB in 2.02 seconds =
84.95 MB/sec
> Timing buffered disk reads: 34 MB in 3.08 seconds =
11.04 MB/sec
>
> Note the big drop of of 3 MB/sec on disk reads.
>
> dmesg (edited) gives:
>
> on 2.4:
> VP_IDE: VIA vt82c586b (rev 41) IDE UDMA33 controller on
pci00:07.1
> hdb: IC35L040AVVN07-0, ATA DISK drive
> hdb: 80418240 sectors (41174 MB) w/1863KiB Cache,
CHS=79780/16/63,
> UDMA(33)
> on 2.6:
> VP_IDE: VIA vt82c586b (rev 41) IDE UDMA33 controller on
pci0000:00:07.1
> hdb: IC35L040AVVN07-0, ATA DISK drive
> hdb: 80418240 sectors (41174 MB) w/1863KiB Cache,
CHS=65535/16/63,
> UDMA(33)
>
> hdparm -i output is identical between the 2 kernels and
hdparm settings
> are identical as follows (except cylinders as above):
>
> Model=IC35L040AVVN07-0, FwRev=VA2OAG0A,
SerialNo=VNP210B2RAP0TB
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
> BuffType=DualPortCache, BuffSize=1863kB, MaxMultSect=16,
MultSect=16
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes,
LBAsects=80418240
> 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 udma5
> AdvancedPM=yes: disabled (255) WriteCache=enabled
> Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1:
>
> multcount = 16 (on)
> IO_support = 1 (32-bit)
> unmaskirq = 1 (on)
> using_dma = 1 (on)
> keepsettings = 0 (off)
> readonly = 0 (off)
> readahead = 8 (on)
> geometry = 79780/16/63, sectors = 80418240, start = 0
>
> I noticed a difference in dmesg:
> on 2.4:
> Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
> on 2.6:
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
>
> Could that make a difference?
>
> Please let me know if you'd like me to run more tests,
patch kernels,
> ..., anything to regain the performance.
>
>
> Many thanks in advance,
>
> --
> Jean-Luc Fontaine
next reply other threads:[~2003-12-25 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-25 16:39 Max Payne [this message]
2003-12-25 18:25 ` Jean-Luc Fontaine
2004-01-10 11:14 ` IDE performance drop between 2.4.23 and 2.6.0: fixed in 2.6.1 Jean-Luc Fontaine
-- strict thread matches above, loose matches on Subject: below --
2003-12-27 14:43 IDE performance drop between 2.4.23 and 2.6.0 Jean-Luc Fontaine
2003-12-27 17:40 ` Linus Torvalds
2003-12-27 19:54 ` Jean-Luc Fontaine
2003-12-25 13:56 Luis Miguel García
2003-12-25 14:35 ` Ed Sweetman
2003-12-25 20:35 ` Luis Miguel García
2003-12-25 5:20 Luis Miguel García
2003-12-24 9:27 Vid Strpic
2003-12-24 15:17 ` Gene Heskett
2003-12-24 17:24 ` Gordon Larsen
2003-12-23 12:42 Jean-Luc Fontaine
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=freemail.20031125173908.53283@fm3.freemail.hu \
--to=max..payne@freemail.hu \
--cc=jfontain@free.fr \
--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 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®