All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Poor responsiveness during disk I/O
Date: Fri, 14 Jan 2005 11:21:27 -0800	[thread overview]
Message-ID: <7f45d9390501141121269b42b2@mail.gmail.com> (raw)

My system is unresponsive and nearly unusable during period of high
disk I/O. hdparm reports it's using UDMA5 (ATA100), so it looks like
everything's up and running. I have a nForce 220-D motherboard
(A7N266-VM), a new 160 GB Maxtor ATA133 drive, and an 80 wire IDE
cable. I've compiled the amd74xx driver into the kernel.

ATA100 suggests a maximum throughput of 100 MB/s. What I should I
expect to see with hdparm -t?   I'm seeing 40 MB/s.

Please cc me in your reply. Thanks,
Shaun

# hdparm -t /dev/hda

/dev/hda:
 Timing buffered disk reads:  132 MB in  3.05 seconds =  43.26 MB/sec
# hdparm -v /dev/hda

/dev/hda:
 multcount    = 16 (on)
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 19929/255/63, sectors = 163928604672, start = 0
# hdparm -i /dev/hda

/dev/hda:

 Model=Maxtor 6Y160P0, FwRev=YAR41BW0, SerialNo=Y45EJ8KE
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 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
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: (null):

 * signifies the current active mode
# cat /proc/ide/amd74xx
----------AMD BusMastering IDE Configuration----------------
Driver Version:                     2.13
South Bridge:                       0000:00:09.0
Revision:                           IDE 0xc3
Highest DMA rate:                   UDMA100
BM-DMA base:                        0xa800
PCI clock:                          33.3MHz
-----------------------Primary IDE-------Secondary IDE------
Prefetch Buffer:              yes                 yes
Post Write Buffer:            yes                 yes
Enabled:                      yes                 yes
Simplex only:                  no                  no
Cable Type:                   80w                 40w
-------------------drive0----drive1----drive2----drive3-----
Transfer Mode:       UDMA       PIO      UDMA       PIO
Address Setup:       30ns      90ns      30ns      90ns
Cmd Active:          90ns      90ns      90ns      90ns
Cmd Recovery:        30ns      30ns      30ns      30ns
Data Active:         90ns     330ns      90ns     330ns
Data Recovery:       30ns     270ns      30ns     270ns
Cycle Time:          20ns     600ns      60ns     600ns
Transfer Rate:   99.9MB/s   3.3MB/s  33.3MB/s   3.3MB/s

             reply	other threads:[~2005-01-14 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 19:21 Shaun Jackman [this message]
2005-01-14 19:57 ` Poor responsiveness during disk I/O Arjan van de Ven
2005-01-14 21:57   ` Shaun Jackman
2005-01-15 14:53     ` Jan Knutar
2005-01-15 18:59       ` Shaun Jackman

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=7f45d9390501141121269b42b2@mail.gmail.com \
    --to=sjackman@gmail.com \
    --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.