From owner-freebsd-stable  Mon Apr 20 09:56:43 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA08924
          for freebsd-stable-outgoing; Mon, 20 Apr 1998 09:56:43 -0700 (PDT)
          (envelope-from owner-freebsd-stable@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 QAA08569;
          Mon, 20 Apr 1998 16:55:43 GMT
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA05910;
	Tue, 21 Apr 1998 02:50:39 +1000
Date: Tue, 21 Apr 1998 02:50:39 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199804201650.CAA05910@godzilla.zeta.org.au>
To: bde@zeta.org.au, mike@smith.net.au
Subject: Re: best wdc0 flags ?
Cc: dburr@POBoxes.com, hardware@FreeBSD.ORG, stable@FreeBSD.ORG,
        Studded@san.rr.com
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk

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

In -current.

>> Setting the multi-block flag is not such a good optimization, since it
>> pessimizes throughput on some drives and it increases interrupt latency.
>
>Can you qualify "some drives" again?  The overall performance 
>improvement in general use is marked, and it decreases interrupt load 
>in the DMA case.

Old drives.

Bruce

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