From owner-freebsd-current Fri May 14 12:37:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1290914CB6 for ; Fri, 14 May 1999 12:37:38 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA17009; Fri, 14 May 1999 21:37:24 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905141937.VAA17009@freebsd.dk> Subject: Re: Alladdin IDE slow? In-Reply-To: <199905140819.DAA05339@home.dragondata.com> from Kevin Day at "May 14, 1999 3:19:40 am" To: toasty@home.dragondata.com (Kevin Day) Date: Fri, 14 May 1999 21:37:24 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kevin Day wrote: > > I'm using an Alladin chipset in a -current machine... > > 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. Hmm, this sounds stange, I have a noard here with the Alladin on it on which I did the support for the ata driver, it works just fine for me at least... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message