From owner-freebsd-arch@FreeBSD.ORG Thu May 26 08:35:23 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 240FB16A41C; Thu, 26 May 2005 08:35:23 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A4B43D70; Thu, 26 May 2005 08:35:15 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring [10.0.0.2]) by itchy.rabson.org (8.13.3/8.12.11) with ESMTP id j4Q8XovP030875; Thu, 26 May 2005 09:33:50 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-arch@freebsd.org Date: Thu, 26 May 2005 09:33:47 +0100 User-Agent: KMail/1.8 References: <20050525.212009.71136852.nyan@jp.FreeBSD.org> <20050525.111945.41668351.imp@bsdimp.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505260933.49013.dfr@nlsystems.com> X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.83/894/Wed May 25 13:53:16 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: arch@freebsd.org, nyan@jp.FreeBSD.org, Marcel Moolenaar Subject: Re: [RFC] remove bus_memio.h and bus_pio.h X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2005 08:35:23 -0000 On Wednesday 25 May 2005 18:40, Marcel Moolenaar wrote: > On May 25, 2005, at 10:19 AM, M. Warner Losh wrote: > > Short answer: > > > > Great idea. > > Seconded. Thirded. > > > Longer, more detailed answer. > > > > The original idea was to provide a hint to busspace that this > > driver only ever used a certain subset of the available mappings so > > it should assume that subset and agressively optimize the code. > > It has also worked against, well, me in the past in that I couldn't > figure out why a driver simply didn't want to work with memio while > it worked perfectly with pio. Then I spotted the bus_pio.h header at > the top and cursed, cursed, cursed. > > I'm all for performance tuning, but the newbus optimization is just > too weird for its own good this way. Hey, don't blame this on newbus - it predates newbus by quite a bit. I seem to remember that this came in with the first import of CAM so you can blame Justin :-)