Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Apr 2008 10:39:18 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Luigi Rizzo <rizzo@iet.unipi.it>
Cc:        pluknet <pluknet@gmail.com>, current@freebsd.org
Subject:   Re: reading kernel tunables from userland ?
Message-ID:  <20080423153918.GC99910@dan.emsphone.com>
In-Reply-To: <20080423115006.GA37818@onelab2.iet.unipi.it>
References:  <20080423100759.GA37110@onelab2.iet.unipi.it> <a31046fc0804230314y473a6423g242e637286794449@mail.gmail.com> <20080423115006.GA37818@onelab2.iet.unipi.it>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Apr 23), Luigi Rizzo said:
> On Wed, Apr 23, 2008 at 02:14:02PM +0400, pluknet wrote:
> > 2008/4/23 Luigi Rizzo <rizzo@iet.unipi.it>:
> > > sorry for the possibly naive question, but is there a way other
> > >  than sysctl to read the value of kernel 'tunable' variables ?
> > >
> > >  E.g. in if_nfe.c i see
> > >
> > >  TUNABLE_INT("hw.nfe.msi_disable", &msi_disable);
> > >  TUNABLE_INT("hw.nfe.msix_disable", &msix_disable);
> > >  TUNABLE_INT("hw.nfe.jumbo_disable", &jumbo_disable);
> > >
> > >  but sysctl is reporting none of them.
> > >
> > >  I seem to remember that there was a separate command to access
> > >  kernel tunables, but cannot remember which one, and neither 'man
> > >  -k tunable' nor a google search return any useful answer...
> > 
> > Perhaps are you about kenv ?
> 
> yes, thanks...

Is there any reason to have TUNABLE_* macros anymore?  A SYSCTL_* macro
with the CTLFLAG_TUN flag does the same thing and also provides sysctl
access.

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080423153918.GC99910>