Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Sep 2011 10:11:56 +0800
From:      Adrian Chadd <adrian@freebsd.org>
To:        Edgar Martinez <emartinez@kbcnetworks.com>
Cc:        "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject:   Re: PANIC - SWBMISS (9.0-CURRENT)
Message-ID:  <CAJ-VmomMZC09KPXJSfSEZCKR1xqoLXAexS469_1qakO0yMVEEw@mail.gmail.com>
In-Reply-To: <957EB052144AA64AB39F7AB268783201022F835FD4@VA3DIAXVS881.RED001.local>
References:  <CAJ-VmomKosb%2B32HPFbEc68WpoZj-iNfna_6m0Rr4-_B3ZkAyOw@mail.gmail.com> <957EB052144AA64AB39F7AB268783201022F835FD4@VA3DIAXVS881.RED001.local>

next in thread | previous in thread | raw e-mail | index | archive | help
On 30 September 2011 10:09, Edgar Martinez <emartinez@kbcnetworks.com> wrote:
> well, i bet lots of other locking shenanigans exist..by default..
>
> its like whomever wrote this, never imagined that more than a single vap per interface was going to be running..
>
> that's for sure going to affect throughput..

It's more likely going to affect stability.

It's cool; I'll see if I can figure it out. Bonus points if you can
figure out why my patch didn't work before I do, I'd like to use
callout_init_mtx() to properly fix the race. :)



Adrian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomMZC09KPXJSfSEZCKR1xqoLXAexS469_1qakO0yMVEEw>