From owner-freebsd-scsi Fri Sep 10 18:38:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 2671015276; Fri, 10 Sep 1999 18:38:28 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id TAA03862; Fri, 10 Sep 1999 19:38:47 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909110138.TAA03862@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 Cc: Andrew Gallatin , "Justin T. Gibbs" , scsi@freebsd.org, gibbs@freebsd.org, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-reply-to: Your message of "Fri, 10 Sep 1999 16:36:35 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Sep 1999 19:38:47 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I would continue to tweak the variable. I assume you tried setting >the read threshold to MIN and the write threshold to MAX? In other >words, don't start a read from host memory until the FIFO is almost >empty, and don't start a write to host memory until the FIFO is almost >full. The assumption here is that PCI is faster than the SCSI bus >speed so we'll get the longest bursts this way. I misread the data book. If you set them both to MAX, then you would get this behavior. The read fifo threshold is based on the amount of empty space in the fifo, not the amount of data in it. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message