[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] PDU_to_tagged_stream consumes 100% CPU even thoug
Re: [Discuss-gnuradio] PDU_to_tagged_stream consumes 100% CPU even though it is throttled!
Thu, 15 Jan 2015 14:57:50 +0100
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
On 01/15/2015 02:26 PM, Sylvain Munaut wrote:
> >Why don't we just delete_head_blocking() and -- block?
> I think this would prevent the flow graph from stopping because it
> would block there indefinitely.
Yes, a friendly cohabitant of this lab just told me to rtfm and also
consider it; I do agree, I think currently this would stop stop() from
> For that to work, the condition variables of each message port would
> have to be poked by the runtime on shutdown.
> That's why I proposed a version of delete_head_blocking with a timeout
> so we can handover control from time to time.
Yeah, but why don't we just poke that variable on stop()? Ignoring the
work calls that might under non-stop() circumstances might occur from
message queue handling would imho be perfectly fine when stop() has been
Re: [Discuss-gnuradio] PDU_to_tagged_stream consumes 100% CPU even though it is throttled!, Marcus Müller, 2015/01/15