From owner-freebsd-stable@FreeBSD.ORG  Mon Nov 19 19:19:11 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2722016A418;
	Mon, 19 Nov 2007 19:19:11 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 7BF9113C467;
	Mon, 19 Nov 2007 19:19:10 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <4741E1B4.7000107@FreeBSD.org>
Date: Mon, 19 Nov 2007 20:19:16 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Ivan Voras <ivoras@freebsd.org>
References: <4741905E.8050300@chistydom.ru>	<20071119140019.V80667@fledge.watson.org>	<4741A3A8.4010803@chistydom.ru>	<20071119152214.J80667@fledge.watson.org>	<4741B648.7090002@chistydom.ru>	<4741D4D2.4090902@FreeBSD.org>	<fhslf4$oss$1@ger.gmane.org>	<4741DC82.1090809@FreeBSD.org>
	<fhsmlj$shg$1@ger.gmane.org>
In-Reply-To: <fhsmlj$shg$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: 2 x quad-core system is slower that 2 x dual core on FreeBSD
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2007 19:19:11 -0000

Ivan Voras wrote:
> Kris Kennaway wrote:
> 
>> It's explained in the MUTEX_PROFILING(9) manpage (LOCK_PROFILING(9) on 7.0)
>>
>>              cnt_hold  The number of times the lock was held and another
>>                        thread attempted to acquire the lock.
>>
>>              cnt_lock  The number of times the lock was already held
>> when this
>>                        point was reached.
> 
> Interesting... why is the page named in UPPERCASE? :)
> 
> finstall:~> locate lock_profiling
> finstall:~> locate LOCK_PROFILING
> /buildcd/livecd/usr/share/man/man9/LOCK_PROFILING.9.gz
> /usr/obj/usr/src/share/man/man9/LOCK_PROFILING.9.gz
> /usr/share/man/man9/LOCK_PROFILING.9.gz
> /usr/src/share/man/man9/LOCK_PROFILING.9

Matching the option name I guess.  Not sure this is the right thing :)

Kris