From owner-freebsd-arch@FreeBSD.ORG Thu Feb 26 10:56:45 2004 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 56C5116A4CE for ; Thu, 26 Feb 2004 10:56:45 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30AFE43D1F for ; Thu, 26 Feb 2004 10:56:42 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <2004022618564101400kl774e>; Thu, 26 Feb 2004 18:56:41 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA07209; Thu, 26 Feb 2004 10:56:39 -0800 (PST) Date: Thu, 26 Feb 2004 10:56:37 -0800 (PST) From: Julian Elischer To: "M. Warner Losh" In-Reply-To: <20040226.113514.94846192.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE cc: des@des.no cc: arch@freebsd.org Subject: Re: per-device sysctls 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: Thu, 26 Feb 2004 18:56:45 -0000 On Thu, 26 Feb 2004, M. Warner Losh wrote: > In message: > des@des.no (Dag-Erling Sm=F8rgrav) writes: > : "M. Warner Losh" writes: > : > How is this different than the sysctl stuff that already exsists for > : > this and is accessed by devinfo? > :=20 > : 1) it is immensely easier to access >=20 > From whose point of view. devinfo is easier to type than sysctl dev > by one character :-). However, it is easier to check a specific thing.. e.g. What's on pcibus 2? sysctl dev.nexus0.acpi0.pcib0.pci0.pcib2.pci2 a bit of a mouthfull, but at least unambiguous :-) it might be possible to also produce some "more succinct" versions. i would like to be able to say sysctl dev.nexus0.acpi0.pcib0.pci0.pcib2.slot2 to see what is there.. This is very close to the device-tree filesystem, (I forget the actual name) that linux has. The advantage of that approach is that you can have symlinks.. e.g. /devtree/nexus0/acpi0/pcib0/pci0/pcib2/pci2/slot2 --> /devtree/nexus0/acpi0/pcib0/pci0/pcib2/pci2/bwe0 of course in human terms the above would be easier read as: /devtree/pcib0/pcib2/slot2 or=20 dev.pcib0.pcib2.slot2 is there a way of getting rid of the "fluff" entries? ( a flag on teh dev_attach saying "I am a fluff entry, do not show me"?) >=20 > : 2) it gives drivers a well-defined place to put their per-device > : sysctl variables - devinfo doesn't address that issue at all >=20 > That is a good reason to transitioning to this, so long as we can come > up with a good way to represent detached nodes. This also gives us a > good place to hang other actions we may want to send to device drivers > like power down, etc. I agree this lays the groundwork for unifying a number of things.. what about 'virtual' devices? dev.virtual.mem dev.virtual.mem.size dev.virtual.kmem >=20 > Warner > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >=20