Date: Wed, 10 Dec 2008 22:24:32 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r185893 - head/sys/kern Message-ID: <20081210221842.V97918@maildrop.int.zabbadoz.net> In-Reply-To: <200812102217.mBAMHAPo044753@svn.freebsd.org> References: <200812102217.mBAMHAPo044753@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Dec 2008, Bjoern A. Zeeb wrote: > Author: bz > Date: Wed Dec 10 22:17:09 2008 > New Revision: 185893 > URL: http://svn.freebsd.org/changeset/base/185893 > > Log: > Make sure nmbclusters are initialized before maxsockets > by running the tunable_mbinit() SYSINIT at SI_ORDER_MIDDLE > before the init_maxsockets() SYSINT at SI_ORDER_ANY. > > Reviewed by: rwatson, zec > Sponsored by: The FreeBSD Foundation > MFC after: 4 weeks The problem was found by Marko Zec during the preparation of the next vimage commit patch. Booting different kernels (w/ and w/o the patch) resulted in different values for net.inet.tcp.maxtcptw and kern.ipc.maxsockets. After careful review it was clear that the intialization values for all relevant variables had not been altered. Further debugging revealed that the order the SYSINITs were run had changed. This has been around for quite a while and worked more or less out of linker luck. /bz -- Bjoern A. Zeeb The greatest risk is not taking one.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081210221842.V97918>