From owner-freebsd-arch@FreeBSD.ORG  Thu Feb 26 12:02:20 2004
Return-Path: <owner-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 71F9016A4CE; Thu, 26 Feb 2004 12:02:20 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E9DB943D1D; Thu, 26 Feb 2004 12:02:19 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i1QK2Hkj081515;
	Thu, 26 Feb 2004 13:02:17 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Thu, 26 Feb 2004 13:02:00 -0700 (MST)
Message-Id: <20040226.130200.112722727.imp@bsdimp.com>
To: des@des.no
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <xzphdxdk690.fsf@dwp.des.no>
References: <Pine.NEB.3.96L.1040226135237.79901X-100000@fledge.watson.org>
	<xzphdxdk690.fsf@dwp.des.no>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
cc: arch@freebsd.org
cc: rwatson@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
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2004 20:02:20 -0000

In message: <xzphdxdk690.fsf@dwp.des.no>
            des@des.no (Dag-Erling Sm=F8rgrav) writes:
: Robert Watson <rwatson@freebsd.org> writes:
: > Having a unified and managed namespace for device sysctls sounds li=
ke a
: > generally good idea to me, as more and more devices require some of=

: > another tweaking.  Have you had any thoughts on how to name sysctls=
 and
: > kernel environment variables on a per-driver basis, rather than a
: > per-device basis?  I.e., fxp and some other device drivers have
: > configuration settings that affect all instances of devices, rather=
 than
: > specific instances.
: =

: It should be easy to add a per-devclass_t or per-driver_t sysctl
: context and tree.  These things are disgustingly easy to create; the
: only hard part is figuring out when and where to create them.

You'd need to have devclass as well as dev trees, but that's easy to
do.  We have hw.tsc.<driver>.<stat> sysctls for all the drivers at
work, and it would be nice to have a more general framework to put
stuff like that into.

It would be nice if there was some kind of tie-in to tunables as well,
since many drivers have tunables that are global, but might want to be
less global.

Warner