Re: [Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Nemanja Savic
You are right, cause I was looking in a process manager and only one core was 100% busy, but since the middle filter had 37k taps it might be that the other two were starving a little bit. BTW, in the shown flograph, I would like to have signal in upper and down paths synchronized, so I introduced

Re: [Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Marcus Müller
If that file does not exist, GNU Radio 3.6.5 would definitely use the thread-per-block scheduler; you can try export GR_SCHEDULER=TPB prior to executing your flow graph from the same shell. In fact, looking at top_block_impl.cc:59 in 3.6.5.1, it seems the scheduler selection isn't read from a conf

Re: [Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Marcus D. Leech
On 05/12/2015 12:52 PM, Nemanja Savic wrote: You are probably right, cause that file doesn't even exist. I looked at default gnuradio-core.conf in conf.d. I suppose that something like that should be written in gnuradi-core.conf, but really nothing. Where can I find which option should be add

Re: [Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Nemanja Savic
@Marcus Mueller: But when I run the shown flowgraph it uses only one core. On Tue, May 12, 2015 at 6:48 PM, Marcus Müller wrote: > What Marcus said; GNU Radio 3.6 with its default scheduler, which is > aptly named thread-per-block scheduler, automatically runs every block in > its own thread, a

Re: [Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Nemanja Savic
You are probably right, cause that file doesn't even exist. I looked at default gnuradio-core.conf in conf.d. I suppose that something like that should be written in gnuradi-core.conf, but really nothing. Where can I find which option should be added? On Tue, May 12, 2015 at 6:33 PM, Marcus D. Lee

Re: [Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Marcus Müller
What Marcus said; GNU Radio 3.6 with its default scheduler, which is aptly named thread-per-block scheduler, automatically runs every block in its own thread, and by default (ie. unless you explicitely specify affinity) lets the OS handle distribution to CPUs; that's the reason GNU Radio applicatio

Re: [Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Marcus D. Leech
On 05/12/2015 12:25 PM, Nemanja Savic wrote: Hi all guys, I have a flowgraph where I have three parallel paths for filtering signal stored in a file. Here the picture of my flowgraph: Inline image 1 I use gnuradio 3.6.5.1. When I run the script it uses only one processor, and since I have 4

[Discuss-gnuradio] No change when set_processor affinity() is used

2015-05-12 Thread Nemanja Savic
Hi all guys, I have a flowgraph where I have three parallel paths for filtering signal stored in a file. Here the picture of my flowgraph: [image: Inline image 1] I use gnuradio 3.6.5.1. When I run the script it uses only one processor, and since I have 4 cores, I would like to run every of the