Re: uipc_sockbuf sysctl



On Saturday 29 September 2007 08:33:12 pm Sam Banks wrote:
Hey all,

I have started looking into cleaning up sysctl's with empty
descriptions and have come across kern.dummy.

Looking into sys/kern/uipc_sockbuf.c, kern.dummy does
absolutely nothing other than offer the ability to change
it. The variable that the sysctl call populates (dummy) is
not used directly in sys/kern/uipc_sockbuf.c or, as far as I
can see, anywhere in the sys/ code.

Is there a reason I'm missing why this seemingly uneeded
sysctl call is in the code or can it be removed with the
attached patch?

Cheers,

It reserves a specific OID value since the old kern.maxsockbuf wasn't
OID_AUTO.

--
John Baldwin
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • uipc_sockbuf sysctl
    ... Hey all, ... I have started looking into cleaning up sysctl's with empty ... The variable that the sysctl call populates is ...
    (freebsd-current)
  • [2.4.x, 2.6 problem] registering of empty /proc/sys dirs leads to leaving pointers to freed memory
    ... (sent to linux-kernel and grsecurity dev) ... Yesterday I got an Oops on somewhat patched 2.4.20 when trying to run ... sysctl_init() in kernel/sysctl.c registers some sysctl tables ... and unregister_proc_tableremoves empty, not used ...
    (Linux-Kernel)
  • Re: KTR ?
    ... daffy@gw:~ %> sysctl ... /tmp/ktr.out is empty & nothing is printed out on console when alq_enable is set to 0. ... Olivier Warin ...
    (freebsd-current)
  • KTR ?
    ... daffy@gw:~ %> sysctl debug.ktr ... /tmp/ktr.out is empty & nothing is printed out on console when alq_enable is set to 0. ... Olivier Warin ...
    (freebsd-current)