Date: Fri, 10 Dec 1999 09:48:12 +0100 (CET) From: Andrzej Bialecki <abial@webgiro.com> To: Archie Cobbs <archie@whistle.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree Message-ID: <Pine.BSF.4.20.9912100934240.76117-100000@mx.webgiro.com> In-Reply-To: <199912092359.PAA76217@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Dec 1999, Archie Cobbs wrote: > Andrzej Bialecki writes: > > I'd like to know whether we reached some conclusions concerning the naming > > of sysctl variables created (or related to) KLDs. I know that Linux > > emulator creates "compat.linux". I don't know if any other module creates > > sysctls (well, except my SPY module.. :-). > > > > So, what is the current thinking? Should we use > > > > modules.my_module.whatever, or > > > > kld.my_kld.whatever, or > > > > just sprinkle the new sysctls randomly over the tree, according to their > > functions, e.g. > > > > kern.my_module_kern_hook > > net.inet.my_module_inet_hook > > ... > > I think the latter. In 'theory' there should be no discernable > difference between functionality from a KLD vs. the same functionality > compiled directly into the kernel. Yes, assuming that the same functionality CAN be compiled in statically. IMHO the kernel modularity is a laudable goal, and if it works well, there are only few cases when you would want to make a monolithic kernel. IMHO, of course :-) > KLD's are just a linking mechanism, and shouldn't have any more > significance than that from a usability perspective. Hah. If it were so simple... Let's take the example of a module foo, which provides unique features of bar and baz. They are unrelated to any already existing category. Where they should be hooked up? kernel? machdep? Then these categories will become a messy, amorphic trashcans. Also, it will be difficult to see which sysctls will disappear when the module is unloaded. Also, if we say that modules should register their sysctls in easily discernible place in the tree, we set up a good example for third party vendors, who otherwise will sprinkle their own sysctls all over the tree... You can probably see from the above what is my preference.. ;-) More or less, my question is: how the sysctl tree will look like when _most_ of the kernel will be in modules? Andrzej Bialecki // <abial@webgiro.com> WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.9912100934240.76117-100000>