Date: Thu, 26 Feb 2004 19:47:01 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: "M. Warner Losh" <imp@bsdimp.com> Cc: arch@freebsd.org Subject: Re: per-device sysctls Message-ID: <xzpu11dk7a2.fsf@dwp.des.no> In-Reply-To: <20040226.113514.94846192.imp@bsdimp.com> (M. Warner Losh's message of "Thu, 26 Feb 2004 11:35:14 -0700 (MST)") References: <xzpk729lnq7.fsf@dwp.des.no> <20040226.112045.82374099.imp@bsdimp.com> <xzp7jy9lmnf.fsf@dwp.des.no> <20040226.113514.94846192.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"M. Warner Losh" <imp@bsdimp.com> writes: > des@des.no (Dag-Erling Sm=F8rgrav) writes: > : 1) it is immensely easier to access > From whose point of view. Programmatically. The in-kernel implementation is much simpler, and the userland code required to access it will also be simpler. Accessing individual devices (once you know where they are) should also be much simpler since devinfo only gives you "all or nothing". > : 2) it gives drivers a well-defined place to put their per-device > : sysctl variables - devinfo doesn't address that issue at all > That is a good reason to transitioning to this, so long as we can come > up with a good way to represent detached nodes. As long as they have a device_t, it should be a piece of cake. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpu11dk7a2.fsf>