This graph doesnt have any unlock/locks in the code itself, it does use valve blocks (which I believe use unlock/lock internally) which are used to mute/unmute streams (there is probably an average of 2-4 valve state changes per second across the graphs 19 valves).
On Tue, Nov 22, 2011 at 8:39 AM, Marcus D. Leech <[email protected]> wrote: > ** > And this is still the flow-graph that has lock/unlock() in it? From the > report of very-high > rescheduling interrupts, I wonder if there's a subtle bug in the Gnu > Radio block > scheduler around lock()/unlock() that causes horrible thrashing. >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
