Date: Fri, 14 May 1999 03:19:40 -0500 (CDT) From: Kevin Day <toasty@home.dragondata.com> To: current@freebsd.org Subject: Alladdin IDE slow? Message-ID: <199905140819.DAA05339@home.dragondata.com>
next in thread | raw e-mail | index | archive | help
I'm using an Alladin chipset in a -current machine... CPU: AMD-K6(tm) 3D processor (337.19-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> real memory = 134217728 (131072K bytes) avail memory = 126808064 (123836K bytes) chip0: <AcerLabs M1541 (Aladdin-V) PCI host bridge> at device 0.0 on pci0 pcib1: <AcerLabs M5243 PCI-PCI bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 isab0: <AcerLabs M1533 portable PCI-ISA bridge> at device 7.0 on pci0 ata-pci0: <AcerLabs Aladdin IDE controller> at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ata0: master: settting up UDMA2 mode on Aladdin chip OK ad0: <QUANTUM FIREBALL SE3.2A/API.0C00> ATA-3 disk at ata0 as master ad0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: settting up UDMA2 mode on Aladdin chip OK ad1: <QUANTUM FIREBALL SE3.2A/API.0C00> ATA-3 disk at ata0 as slave ad1: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode ata1: master: settting up UDMA2 mode on Aladdin chip OK ad2: <QUANTUM FIREBALL SE3.2A/API.0C00> ATA-3 disk at ata1 as master ad2: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ata1: slave: settting up UDMA2 mode on Aladdin chip OK ad3: <Maxtor 91728D8/GAS54112> ATA-4 disk at ata1 as slave ad3: 16479MB (33750864 sectors), 33483 cyls, 16 heads, 63 S/T, 512 B/S ad3: piomode=4, dmamode=2, udmamode=2 ad3: 16 secs/int, 0 depth queue, DMA mode ad3 is the one getting the heaviest use, from me... However, I notice a few things from when I went to the ata driver, from a 3.1 kernel using the wd0 driver. The drive is now much slower... While I don't have numbers either way, this system acts as a nfs server. Not only are the NFS clients acting slower after my switch, but nearly all my nfsd's are sitting in biord or biowr now, where before they were usually idle. Also, the IDE LED on the case/motherboard is now acting kinda erratic. I can hear the HD doing accesses when the light is off, and at times the light seems to stay on for 2-3 seconds, when there's no activity. (This didn't happen under wd0)... Is this a case of DMA just not working well for me, or is there a magic flag I'm missing? This is -current from about a week ago. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905140819.DAA05339>