Advice on a multithreaded netisr patch?

[Barney Cordoba]

--- On Wed, 4/8/09, Barney Cordoba <barney_cordoba at yahoo.com> wrote:

> From: Barney Cordoba <barney_cordoba at yahoo.com>
> Subject: Re: Advice on a multithreaded netisr  patch?
> To: "Robert Watson" <rwatson at FreeBSD.org>
> Cc: freebsd-net at freebsd.org, "Ivan Voras" <ivoras at freebsd.org>
> Date: Wednesday, April 8, 2009, 9:18 AM
> --- On Tue, 4/7/09, Robert Watson
> <rwatson at FreeBSD.org> wrote:
> 
> > From: Robert Watson <rwatson at FreeBSD.org>
> > Subject: Re: Advice on a multithreaded netisr  patch?
> > To: "Barney Cordoba"
> <barney_cordoba at yahoo.com>
> > Cc: freebsd-net at freebsd.org, "Ivan Voras"
> <ivoras at freebsd.org>
> > Date: Tuesday, April 7, 2009, 8:56 AM
> > 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.
> 
> What are the units for lock profiling? For example, the
> "average
> wait" is in what units? 
> 
> Is there a way to reset the stats counters? If not, it
> might be nifty if 
> toggling prof.enable reset the stats to run some different
> kinds of
> tests without rebooting.
> 
> Barney

I know, I know. Read the man page...