From owner-freebsd-current Thu Apr 9 10:25:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11614 for freebsd-current-outgoing; Thu, 9 Apr 1998 10:25:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from slip-3 (mail@slip-3.slip.net [207.171.193.17]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA11608 for ; Thu, 9 Apr 1998 10:25:46 -0700 (PDT) (envelope-from thomma@slip.net) Received: from thomma by slip-3 with local (Exim 1.62 #4) id 0yNL4b-0002IT-00; Thu, 9 Apr 1998 10:25:13 -0700 Subject: FAILSAFE and NCR To: freebsd-current@FreeBSD.ORG Date: Thu, 9 Apr 1998 10:25:08 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Tamiji Homma Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I posted about SCSI disk performance difference(three times) between 19980222-SNAP and 19971006-SNAP. It turned out to be the FAILSAFE option made the difference. It slows SCSI disk access down significantly. Thanks to Geoff Buckingham and John Dyson, I could dig into a little deeper. I noticed that MAX_START is now hardcoded to 32, which used to be (MAX_TARGET + 7 * SCSI_NCR_DFLT_TAGS) in sys/pci/ncr.c. Is this going to be this way from now on? Or is it anything to do with CAM? So that it will be resolved differently? It is a little annoying everytime I have to patch sys/pci/ncr.c. Thanks Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message