Date: Thu, 26 Feb 2004 13:02:00 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: des@des.no Cc: rwatson@freebsd.org Subject: Re: per-device sysctls Message-ID: <20040226.130200.112722727.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040226.130200.112722727.imp>