From owner-freebsd-scsi Fri Dec 3 10:11:39 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 8CD1B15211 for ; Fri, 3 Dec 1999 10:11:27 -0800 (PST) (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 KAA00529; Fri, 3 Dec 1999 10:12:07 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199912031712.KAA00529@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: mjacob@feral.com Cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-reply-to: Your message of "Fri, 03 Dec 1999 09:55:51 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Dec 1999 10:12:07 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> The bounce buffering code doesn't perform coalessing of data yet because >> I never found an algorithm I liked for it. The NetBSD approach of >> making the bounce buffer 64K big and copying the whole thing if any >> portion needs to be bounced doesn't appeal to me (it doesn't scale >> well and consumes much too much memory). > >You pay for what you get. If you are really still using ISADMA mass >storage, blow 128k or MAXPHYS already.. IMO... We do, but we allocate and dole it out as individual pages. NetBSD allocates MAXPHYS per possible transaction on each card which turns out to be 1MB of < 16MB memory per card. This doesn't scale. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message