From owner-freebsd-current Thu Apr 4 19:21:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id A8DC037B405 for ; Thu, 4 Apr 2002 19:21:21 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g353Ku971739; Thu, 4 Apr 2002 20:21:01 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200204050321.g353Ku971739@aslan.scsiguy.com> To: mjacob@feral.com Cc: Terry Lambert , Andrew Gallatin , freebsd-current@freebsd.org Subject: Re: BUS_SPACE_MAXSIZE & isp driver. In-Reply-To: Your message of "Thu, 04 Apr 2002 17:17:51 PST." Date: Thu, 04 Apr 2002 20:20:56 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >BUS_SPACE_MAXSIZE seems to be related to the 'largest xfer you will be allowed >to do at one time'- which is wrong because MAXPHYS is larger. If you look at the x86 implementation, BUS_SPACE_MAXSIZE is only used in the non-GNUC case and is not referenced (I don't think) by any driver code. Even setting it to MAXPHYS is not truely correct since at some point we will have to start supporting transfer mappings that are larger than what can be mapped by a single buffer. I never realized that there was such controversy over this value... it was just put in so that I could have something for the non-GNUC case. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message