From owner-freebsd-current@FreeBSD.ORG  Mon Mar 26 20:59:00 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 634BE16A566;
	Mon, 26 Mar 2007 20:58:58 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
	[66.23.211.162])
	by mx1.freebsd.org (Postfix) with ESMTP id 3207813C46E;
	Mon, 26 Mar 2007 20:58:56 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1])
	(authenticated bits=0)
	by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l2QKwEWS015293;
	Mon, 26 Mar 2007 15:58:34 -0500 (EST) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Date: Mon, 26 Mar 2007 15:13:26 -0400
User-Agent: KMail/1.9.6
References: <45F388D4.2080900@elischer.org> <45F45172.8070601@elischer.org>
	<86r6rt6z27.fsf@dwp.des.no>
In-Reply-To: <86r6rt6z27.fsf@dwp.des.no>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200703261513.27148.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]);
	Mon, 26 Mar 2007 15:58:36 -0500 (EST)
X-Virus-Scanned: ClamAV 0.88.3/2934/Mon Mar 26 15:04:46 2007 on
	server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no>,
	Julian Elischer <julian@elischer.org>,
	FreeBSD Current <current@freebsd.org>
Subject: Re: netstat wierdness?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2007 20:59:01 -0000

On Tuesday 13 March 2007 09:41:20 am Dag-Erling Sm=F8rgrav wrote:
> Julian Elischer <julian@elischer.org> writes:
> > answering myself..
> > comes from having options LOCK_PROFILING in my kernel.
> > adding the same to /etc/make.conf and recompiling netstat and libkvm=20
helped.
> > (not sure if both are needed)
>=20
> This is very bad.  LOCK_PROFILING should have no visible effect on
> userland.  That is precisely what xinpcb, xunpcb, xtcpcb etc. are for:
> to isolate userland from kernel structures.  They should not contain
> any locks or anything else which would be affected by LOCK_PROFILING
> or other kernel options.

LOCK_PROFILING (and it's predecessor MUTEX_PROFILING) have always resulted =
in=20
variant object sizes in the kernel.  They shouldn't be visible to userland=
=20
though, and fixing xfoo is the right step IMHO.

=2D-=20
John Baldwin