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 applications tend to scale very well on multiple CPUs, even if the algorithms in the individual blocks are not heavily multithreaded.
Greetings, Marcus On 05/12/2015 06:33 PM, Marcus D. Leech wrote: > 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 cores, I would like to run every of the >> paths on another processor. For every filter I do >> set_processr_affinity[some number between 0 and ]. When I run the >> script nothing changes, it still runs on a single core. Am I missing >> something with set_processor_affinity method? >> >> Best, >> >> -- >> Nemanja Savić >> >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > My guess is that your ~/.gnuradio/config.conf specifies to use the > single-threaded scheduler. > > > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
