discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] PDU_to_tagged_stream consumes 100% CPU even thoug


From: Ludwig Stephan (CR/AEH4)
Subject: Re: [Discuss-gnuradio] PDU_to_tagged_stream consumes 100% CPU even though it is throttled!
Date: Thu, 15 Jan 2015 08:13:21 +0000

Hi List,

from my understanding of the code, this caveat still exists. And I have the 
same problem with this block as Achilleas.

Johnathan: As you wrote in the cited post that you would be working on that 
after 3.7.0, could you please give an update on the state of work?
How can we support?

Mit freundlichen Grüßen / Best regards

 Stephan Ludwig

Robert Bosch GmbH
Corporate Sector Research & Advance Engineering, Communication Technology 
(CR/AEH4) 
Renningen
70465 Stuttgart
GERMANY
www.bosch.com

Tel. +49(711)811-8809
Fax +49(711)811-1052
Mobil +49(172)5630639
address@hidden

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; 
Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar 
Denner, 
Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, Dr. Dirk 
Hoheisel, Christoph Kübel, 
Uwe Raschke, Wolf-Henning Scheider, Dr. Werner Struth, Peter Tyroller


-----Ursprüngliche Nachricht-----
Von: address@hidden [mailto:address@hidden Im Auftrag von Bastian Bloessl
Gesendet: Donnerstag, 15. Januar 2015 07:15
An: address@hidden; address@hidden
Betreff: Re: [Discuss-gnuradio] PDU_to_tagged_stream consumes 100% CPU even 
though it is throttled!

Hi,

On 01/14/2015 11:29 PM, Achilleas Anastasopoulos wrote:
> I have the following problem that is been bugging me for quite some time
> now,
> and I would like to solicit your help.
>
> I made a hier block in GRC (called "test_pdu_to_tag") with:
>
> pad_source--->pdu_to_tagged_stream-->pad_sink
>
> (I also made the pad_source "optional" and the pad_sink "required")
>
> After compiling this block, I test it using the following GRC test
>
> test_pdu_to_tag-->throttle (at 100Hz!)-->null_sink
>
> (observe that the "test_pdu_to_tag" does not have an input)
>
> ==============
> When I run this I get that the CPU load goes to 100%.
>
> can anyone help me figure out why this is happening?
> This is all with the latest master on a Fedora 19.


AFAIK, pdu_to_tagged_stream is busy-waiting for new PDUs (at least in 
June 2013 it was) and always uses 100% CPU.

http://lists.gnu.org/archive/html/discuss-gnuradio/2013-06/msg00552.html

Best,
Bastian


_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



reply via email to

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