Date: Tue, 7 Apr 2009 16:01:50 -0700 (PDT) From: Barney Cordoba <barney_cordoba@yahoo.com> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-net@freebsd.org, Ivan Voras <ivoras@freebsd.org> Subject: Re: Advice on a multithreaded netisr patch? Message-ID: <362116.58661.qm@web63908.mail.re1.yahoo.com> In-Reply-To: <alpine.BSF.2.00.0904072352250.85326@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--- On Tue, 4/7/09, Robert Watson <rwatson@FreeBSD.org> wrote:
> From: Robert Watson <rwatson@FreeBSD.org>
> Subject: Re: Advice on a multithreaded netisr patch?
> To: "Barney Cordoba" <barney_cordoba@yahoo.com>
> Cc: freebsd-net@freebsd.org, "Ivan Voras" <ivoras@freebsd.org>
> Date: Tuesday, April 7, 2009, 6:52 PM
> On Tue, 7 Apr 2009, Barney Cordoba wrote:
>
> >>> 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.
> >
> > It might be good to mention this in the man page. Most
> 3rd party drivers build stand-alone, and even if you pull
> down the latest drivers from intel or broadcom they're
> usually built out of the kernel build. Its pretty
> frustrating to have random things failing, mbuf leaks, etc
> without any warning.
>
> From the man page:
>
> NOTES
> The LOCK_PROFILING option increases the size of struct
> lock_object, so a
> kernel built with that option will not work with
> modules built without
> it
Nevermind. Obviously I just plain missed it.
BC
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?362116.58661.qm>