From owner-freebsd-arch@FreeBSD.ORG Thu Dec 11 16:29:17 2003 Return-Path: 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 9380616A4CE for ; Thu, 11 Dec 2003 16:29:17 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26D1143D33 for ; Thu, 11 Dec 2003 16:29:16 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 482F965319; Fri, 12 Dec 2003 00:29:14 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 86516-04; Fri, 12 Dec 2003 00:29:13 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id E79F16530E; Fri, 12 Dec 2003 00:29:09 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 799DA2F; Fri, 12 Dec 2003 00:29:05 +0000 (GMT) Date: Fri, 12 Dec 2003 00:29:02 +0000 From: Bruce M Simpson To: "M. Warner Losh" Message-ID: <20031212002902.GB83410@saboteur.dek.spc.org> References: <20031211145311.Q51054@root.org> <20031211.162119.128604849.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031211.162119.128604849.imp@bsdimp.com> cc: arch@freebsd.org cc: nate@root.org Subject: Re: Common device driver classes? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 00:29:17 -0000 I'm tracking the outcome of this discussion so I know where to put things like cache geometry discovery. My original plan was to assume uniform cache and TLB geometry across all CPUs in the system. This may not be the case. In which case implementing it via ivars may be more appropriate if Nate chooses to go down this road -- but this leaves the problem of how to export these properties easily to the userland. This is to facilitate getting at these properties a bit easier and machine-independent (I note that the current NDIS and PowerPC efforts could probably use this stuff). BMS