From owner-freebsd-net@FreeBSD.ORG  Tue Apr  7 12:56:02 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C945A10656D4;
	Tue,  7 Apr 2009 12:56:02 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id A27BF8FC22;
	Tue,  7 Apr 2009 12:56:02 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
	by cyrus.watson.org (Postfix) with ESMTPS id 3ED3F46B9D;
	Tue,  7 Apr 2009 08:56:02 -0400 (EDT)
Date: Tue, 7 Apr 2009 13:56:02 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Barney Cordoba <barney_cordoba@yahoo.com>
In-Reply-To: <952316.35609.qm@web63906.mail.re1.yahoo.com>
Message-ID: <alpine.BSF.2.00.0904071354521.45341@fledge.watson.org>
References: <952316.35609.qm@web63906.mail.re1.yahoo.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-net@freebsd.org, Ivan Voras <ivoras@freebsd.org>
Subject: Re: Advice on a multithreaded netisr  patch?
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 12:56:04 -0000


On Tue, 7 Apr 2009, Barney Cordoba wrote:

>> Have you tried LOCK_PROFILING?  It would quickly tell you if driver locks 
>> were a source of significant contention.  It works quite well...
>
> When I enabled LOCK_PROFILING my side modules, such as if_ibg, stopped 
> working. It seems that the ifnet structure or something changed with that 
> option enabled. Is there a way to sync this without having to integrate 
> everything into a specific kernel build?

LOCK_PROFILING changes the size of lock-related data structures, so requires 
both kernel and full set of modules to be rebuilt with the option.

Robert N M Watson
Computer Laboratory
University of Cambridge