Date: Thu, 26 Feb 2004 20:43:48 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Cc: arch@freebsd.org Subject: Re: per-device sysctls Message-ID: <2324.1077824628@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 26 Feb 2004 19:47:01 %2B0100." <xzpu11dk7a2.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzpu11dk7a2.fsf@dwp.des.no>, Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= writes: >"M. Warner Losh" <imp@bsdimp.com> writes: >> des@des.no (Dag-Erling Smørgrav) 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. Having a device_t is a property of having hardware, not of being a device driver. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2324.1077824628>