Re: [Discuss-gnuradio] fftw3 thread safety ?

[Tom Tsou]

On Wed, Aug 13, 2014 at 8:35 AM, jmfriedt
<address@hidden> wrote:
> I tracked the issue to the fftw3 thread safety and apparently some
> global variable shared by all task planners. Can someone point me to
> the way gnuradio solves this thread safety issue (which must be solved
> since I can use as many FFT display blocks I want) ? The semaphore
> solution is not really satisfactory since I'd like not to ask my block
> to wait for all other data processing to be completed before I can
> complete its own task.

I have just a general thought on fftw. The plan - during generation -
is the only part of fftw that must be explicitly protected or run from
a single thread. If you're calling execute on the same plan from
multiple threads, or different plans that share the same memory, then
that memory needs protection to prevent garbled samples. Otherwise, no
thread protection should be necessary for the execution call.

  -TT