All of
 help / color / mirror / Atom feed
From: Kresimir Kukulj <>
To: Alan Cox <>
Cc: Linux Kernel Mailing List <>
Subject: Re: [PATCH] siimage.c - turning DMA on because of 'md' kernel thread.
Date: Mon, 21 Jul 2003 17:34:08 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Quoting Alan Cox (
> On Gwe, 2003-07-18 at 23:34, Kresimir Kukulj wrote:
> > resync.  That means that disks are busy (in PIO mode), and when hdparm -d1 -X69
> > executes, system freezes [if there is no disk/little activity hdparm cludge
> > passes ok - for example, if RAID-1 is clean so there is no resync].
> The newest driver should put them into DMA automatically and set the
> limit. The other changes I'll check over but certainly look like they
> may be needed.

Hm, I tried 2.4.22-pre7 and it did not set disks to DMA mode, but it did set
the limit (max_kb_per_request). With the following modification, kernel
(2.4.22-pre7) initializes both disk to UDMA133, and as far as I can see, it
works ok.

In siimage.c there is a check for Maxtor disks - they are/should be set to
UDMA100.  Is this also necessary for Seagate SATA disks ?

--- siimage.c.orig      Mon Jul 21 15:13:16 2003
+++ siimage.c   Mon Jul 21 16:56:28 2003
@@ -488,7 +488,7 @@
        struct hd_driveid *id   = drive->id;
        if ((id->capability & 1) != 0 && drive->autodma) {
-               if (!(hwif->atapi_dma))
+               if ((hwif->atapi_dma))
                        goto fast_ata_pio;
                /* Consult the list of known "bad" drives */
                if (hwif->ide_dma_bad_drive(drive))

And it looks like:

SiI3112 Serial ATA: IDE controller at PCI slot 02:04.0
PCI: Found IRQ 5 for device 02:04.0
PCI: Sharing IRQ 5 with 02:00.0
SiI3112 Serial ATA: chipset revision 2
SiI3112 Serial ATA: not 100% native mode: will probe irqs later
    ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
    ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
hde: ST3120023AS, ATA DISK drive
blk: queue c0326ef8, I/O limit 4095Mb (mask 0xffffffff)
hdg: ST3120023AS, ATA DISK drive
blk: queue c0327364, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xf8800080-0xf8800087,0xf880008a on irq 5
ide3 at 0xf88000c0-0xf88000c7,0xf88000ca on irq 5
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=232581/16/63, UDMA(133)
hdg: attached ide-disk driver.
hdg: host protected area => 1
hdg: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=232581/16/63, UDMA(133)

 multcount    = 16 (on)
 I/O support  =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 14593/255/63, sectors = 234441648, start = 0
 busstate     =  1 (on)

        LBA, IORDY(can be disabled)
        Buffer size: 8192.0kB   ECC bytes: 4    Queue depth: 1
        Standby timer values: spec'd by standard
        r/w multiple sector transfer: Max = 16  Current = 16
        Advanced power management level: 65278
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=240ns  IORDY flow control=120ns

# hdparm -tT /dev/md3

 Timing buffer-cache reads:   128 MB in  0.24 seconds =533.33 MB/sec
 Timing buffered disk reads:  64 MB in  2.42 seconds = 26.45 MB/sec

[One plex]
# hdparm -tT /dev/hde3

 Timing buffer-cache reads:   128 MB in  0.24 seconds =533.33 MB/sec
 Timing buffered disk reads:  64 MB in  1.82 seconds = 35.16 MB/sec

Poor results, but at least it works.

Kresimir Kukulj            
Old PC's never die. They just become Unix terminals.

      reply	other threads:[~2003-07-21 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 22:34 [PATCH] siimage.c - turning DMA on because of 'md' kernel thread Kresimir Kukulj
2003-07-18 22:48 ` Alan Cox
2003-07-21 15:34   ` Kresimir Kukulj [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.