Date: Fri, 27 Feb 2004 23:16:09 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no> Cc: arch@freebsd.org Subject: Re: per-device sysctls Message-ID: <20040227230124.D2469@gamplex.bde.org> In-Reply-To: <xzp7jy9lmnf.fsf@dwp.des.no> References: <xzpk729lnq7.fsf@dwp.des.no> <20040226.112045.82374099.imp@bsdimp.com> <xzp7jy9lmnf.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Feb 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: > "M. Warner Losh" <imp@bsdimp.com> writes: > > How is this different than the sysctl stuff that already exsists for > > this and is accessed by devinfo? > > 1) it is immensely easier to access > > 2) it gives drivers a well-defined place to put their per-device > sysctl variables - devinfo doesn't address that issue at all Only broken drivers use sysctl variables. ioctl(3) is a much better interface that sysctl(3) for accessing per-device info. sysctl(8) is a better interface than ioctl(8) for handling the few device control things that can be done in a generic way, but this is only because there are so few such things that ioctl(8) doesn't exist. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040227230124.D2469>