Date: Fri, 05 Aug 2005 11:24:34 -0600 From: Scott Long <scottl@samsco.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, Dan Nelson <dnelson@allantgroup.com> Subject: Re: Checking sysctl values from within the kernel. Message-ID: <42F3A0D2.7090402@samsco.org> In-Reply-To: <200508051101.33927.jhb@FreeBSD.org> References: <20050805005543.5bd947f2.thib@mi.is> <20050805145046.GB78669@dan.emsphone.com> <200508051101.33927.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Friday 05 August 2005 10:50 am, Dan Nelson wrote: > >>In the last episode (Aug 05), Thordur I. Bjornsson said: >> >>>If I want to check a sysctl value from within the kernel (e.g. an >>>KLD), should I use the system calls described in sysctl(3) ? >>> >>>If not, what is the propper way to do so ? >> >>Since most sysctls are direct mappings onto integer variables in the >>kernel, just check the variable directly. > > > There's also a kernel_sysctl() function available in the kernel for in-kernel > access to sysctls. You might have to lookup the OID for a given name > yourself though. Actually, there's a kernel_sysctlbyname() as well. > Shoot, forgot about that function. However, exporting data throughout the kernel via the sysctl interface sounds like poor design. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42F3A0D2.7090402>