# GNURadio scheduler

**URL:** <https://www.ruby-forum.com/t/gnuradio-scheduler/241652>\
**Category:** GNU Radio\
**Created:** [April 21, 2015, 11:46am UTC](https://www.ruby-forum.com/t/gnuradio-scheduler/241652 "2015-04-21T11:46:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [April 21, 2015, 11:46am UTC](https://www.ruby-forum.com/t/gnuradio-scheduler/241652/1 "2015-04-21T11:46:00Z")

</div>

Is there a sample routine, document or youtube video explaining the  
GNUradio scheduler? hard to fully understand Gnuradio without it. What  
are the files in the Gnuradio that are the core of the scheduler?

thanks,

---

<div class="post-metadata">

**Author:** ![Trek](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/7feea3/32.png) [@Trek](https://www.ruby-forum.com/u/Trek)\
**Post date:** [April 21, 2015, 12:47pm UTC](https://www.ruby-forum.com/t/gnuradio-scheduler/241652/2 "2015-04-21T12:47:45Z")

</div>

Hi Trek,

the scheduler and all the core components holding GNU Radio together are  
in gnuradio/gnuradio-runtime. The scheduler is mainly composed of the  
files starting with tpb (==thread per block), block\_executor, and  
block/buffer.

There’s

> **[Explaining the GNU Radio Scheduler — Rondeau Research](http://www.trondeau.com/blog/2013/9/15/explaining-the-gnu-radio-scheduler.html)**
>
> The most important and distinguishing piece of GNU Radio is the underlying scheduler and framework for implementing and connecting the signal processing blocks. While there are many other libraries of DSP blocks available, it's GNU Radio's scheduler...

, and especially the presentation linked therein. Though it’s from 2013,  
the flowcharts on the scheduler’s workings are still valid; you’ll have  
to add message handling in the block iteration, but other than that, I  
don’t think much has changed.

Other than that: The source code is really its best documentation.  
Really, compared to most projects I came across, our source files are  
vividly commented, and the list is almost always eager to both explain  
concepts and questions regarding any particular line of code, so just  
ask 🙂

Greetings,  
Marcus