From owner-freebsd-hardware Mon Apr 20 09:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04639 for freebsd-hardware-outgoing; Mon, 20 Apr 1998 09:43:42 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04481 for ; Mon, 20 Apr 1998 16:43:12 GMT (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id RAA11831; Mon, 20 Apr 1998 17:42:38 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <353B7AEC.D560BAD7@tdx.co.uk> Date: Mon, 20 Apr 1998 17:42:20 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Mike Smith CC: hardware@FreeBSD.ORG Subject: Re: best wdc0 flags ? References: <199804201626.JAA00670@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > >> > I tried those flags and noticed that it turned on 32-bit transfers for > > >> >my wd0, resulting in a 20% increase in throughput. Out of curiosity, why > > >> >aren't these flags included in GENERIC? > > >> > > >> Becuase they break operation of drives that don't support them. > > > > > >Do we have any examples of controllers that don't? > > > > I thought I did, but my oldest accessible drive (all 400MB of it from > > 4 years ago) supports them. The probe seems to handle any that don't. > > OK. Should we make it the default then? Not a good idea... 32 bit transfers cause my nice shiny new Fireball 4.3Gb SE's to barf (this is on a 440FX chipset 'embeded' controller). A bit annoying - but probably expected from Quantum... Kp -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message