From owner-freebsd-hardware  Mon Apr 20 01:30:38 1998
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA06230
          for freebsd-hardware-outgoing; Mon, 20 Apr 1998 01:30:38 -0700 (PDT)
          (envelope-from owner-freebsd-hardware@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06171;
          Mon, 20 Apr 1998 08:30:25 GMT
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA15511;
	Mon, 20 Apr 1998 18:27:45 +1000
Date: Mon, 20 Apr 1998 18:27:45 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199804200827.SAA15511@godzilla.zeta.org.au>
To: dburr@POBoxes.com, Studded@san.rr.com
Subject: Re: best wdc0 flags ?
Cc: hardware@FreeBSD.ORG, stable@FreeBSD.ORG
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

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

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message