From owner-freebsd-arch@FreeBSD.ORG Wed Jul 11 17:53:25 2007 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF43216A468; Wed, 11 Jul 2007 17:53:25 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D6E5213C468; Wed, 11 Jul 2007 17:53:25 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id AE8491A4DA5; Wed, 11 Jul 2007 10:53:25 -0700 (PDT) Date: Wed, 11 Jul 2007 10:53:25 -0700 From: Alfred Perlstein To: Alexander Leidinger Message-ID: <20070711175325.GQ45894@elvis.mu.org> References: <20070711190546.4b202080@deskjail> <57627.1184175231@critter.freebsd.dk> <20070711195110.48820aff@deskjail> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070711195110.48820aff@deskjail> User-Agent: Mutt/1.4.2.3i Cc: Rui Paulo , Shteryana Shopova , "Constantine A. Murenin" , Poul-Henning Kamp , Robert Watson , freebsd-arch@FreeBSD.org Subject: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD 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: Wed, 11 Jul 2007 17:53:26 -0000 * Alexander Leidinger [070711 10:49] wrote: > Quoting "Poul-Henning Kamp" (Wed, 11 Jul 2007 17:33:51 +0000): > > > In message <20070711190546.4b202080@deskjail>, Alexander Leidinger writes: > > >Quoting "Poul-Henning Kamp" (Wed, 11 Jul 2007 13:54:40 +0000): > > > > >You are focusing on physical devices which are specially build as a > > >sensor for some specific stuff. I put my focus on the kernel framework > > >which allows to unify the handling of sensoric data from kernel > > >devices. > > > > I'm trying to point out that your kernel framework belongs in userland. > > It's not my framework. > > > There is no benefit from having it in the kernel. > > You need to get some information out of the kernel somehow (you cut > this part of my mail). And as far as I understand the high level > description (presentation in the net) of this framework, this does this > in an unified way. Do you propose to get the information out of the > kernel in a non-uniform way? Possibly, one way to do that is to provide a well thought out userland library that can make for a nice interface. If by doing it userland the kernel implementation can be kept smaller and more simple it might be a win. That said, it may be a loss if you wind up having to duplicate work over and over for different devices it may be a loss. Remember, once the kernel interface is exposed it has to be there almost forever, while a userland interface and much more easily be adapted. -- - Alfred Perlstein