[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] Threads / GUI

From: 'Eric Blossom'
Subject: [Discuss-gnuradio] Threads / GUI
Date: Fri, 16 Nov 2001 18:05:38 -0800
User-agent: Mutt/1.2.5i

On Fri, Nov 16, 2001 at 05:34:48PM -0800, Ettus, Matt wrote:
> I think single is faster, but I went with double as you said

Out of curiosity, have you benchmarked single vs double?  The only
reason I can imagine single being faster is lower memory bandwidth.

> The symlinks worked, and everything compiled.  Thanks.


> I don't have SMP on my main dev machine, but the one I use for signal
> processing is a dual PIII.


FYI, the current build tree has thread support disabled.  The GUI code
is currently not thread safe and is quite wiggy with threads enabled.

Here's my current thinking on sorting out that problem:

In all VrSigProc's and subclasses, the forecast routine is always run
single threaded.  work is multi threaded.  I'm thinking about adding a
thread safe message queue to each VrSigProc and then have the GUI code
(which will run in a single thread) post messages to the message
queue.  Other code would be free of course to post messages too.  In
addition, I'll add a new method, say "HandleMessage" that will be
invoked when the VrSigProc is known to be single threaded.  This
should have each VrSigProc handle requests gracefully, and avoid the
problems with the GUI code blindly manipulating state.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]