[asterisk-dev] Channel locking/unlocking

[Hans Petter Selasky]

On Thursday 05 April 2007 10:57, Vazir wrote:
> But regarding the current versions is that normal? Please
> note that * was compiled with DEBUG_CHANNEL_LOCKS,
> DETECT_DEADLOCKS and DONT_OPTIMIZE flags to find out why
> zaptel becoming unusable after a while of operation.
>
> On 5 April 2007 13:48, you wrote:
> > On Thursday 05 April 2007 10:02, Anton wrote:
> > > Guys,
> > > trying to find origin of regular the zaptel lockups,
> > > is that amount of channel locks/unlocks normal? It's
> > > generating gigabytes of log details in a few hours
> > > Asterisk 1.4.2+latest 1.4 zaptel svn
> >
> > What you need to do is to make a dynamic list of all the
> > mutexes used. Then you need to figure out the locking
> > order, and see if the locking order is reversed. The
> > FreeBSD project has this feature in the kernel, and it is
> > very useful.
> >

The Asterisk channels are locked/unlocked for every frame that is transferred. 
So you should see at least:

"2*channels*controllers*interrupt_rate" messages per second

--HPS