From owner-freebsd-stable@FreeBSD.ORG Fri May 20 18:37:39 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7B7916A4CE; Fri, 20 May 2005 18:37:39 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45FD243D41; Fri, 20 May 2005 18:37:39 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 974FE51418; Fri, 20 May 2005 11:37:38 -0700 (PDT) Date: Fri, 20 May 2005 11:37:38 -0700 From: Kris Kennaway To: Gleb Smirnoff Message-ID: <20050520183738.GA53549@xor.obsecurity.org> References: <20050515120007.GA777@obiwan.tataz.chchile.org> <20050518155130.H87264@carver.gumbysoft.com> <20050519125639.GK818@obiwan.tataz.chchile.org> <20050520080435.GB26938@cell.sick.ru> <20050520131031.GU818@obiwan.tataz.chchile.org> <20050520131536.GA30219@cell.sick.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <20050520131536.GA30219@cell.sick.ru> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@FreeBSD.org cc: Jeremie Le Hen Subject: Re: panic in recent RELENG_5 tcp code path X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2005 18:37:39 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 20, 2005 at 05:15:36PM +0400, Gleb Smirnoff wrote: > Jeremie, >=20 > On Fri, May 20, 2005 at 03:10:32PM +0200, Jeremie Le Hen wrote: > J> > according to the fact that the panic occured in dereferncing mbuf po= inter > J> > your kernel is compiled without INVARIANTS. > J> >=20 > J> > Please compile it with INVARIANTS. This will probably help to trigge= r panic > J> > earlier, and it will be more clear. > J>=20 > J> a quick look at src/conf/NOTES reveals the following : > J> %%% > J> # > J> # The INVARIANTS option is used in a number of source files to ena= ble > J> # extra sanity checking of internal structures. This support is n= ot > J> # enabled by default because of the extra time it would take to ch= eck > J> # for these conditions, which can only occur as a result of > J> # programming errors. > J> # > J> %%% > J>=20 > J> I'm going to recompile my kernel with INVARIANTS but I wonder in > J> which order of magniture it will slow my kernel down. In other words, > J> what does INVARIANTS do concretely, shall I expect a performance drop > J> like WITNESS does ? >=20 > No. The performance loss is _much_ less significant than in WITNESS case. > You probably will not notice it. Actually, INVARIANTS causes about a 10% penalty on wall clock time on 5.x and above. Kris --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCji5yWry0BWjoQKURAkVtAKDt6zHM02MVP1ihb1TWEZW+qNAIVwCeMuVL u16geNFXPmV7Ny+QsI41EZI= =337V -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU--