diff options
| author | Johnathan Corgan <johnathan@corganlabs.com> | 2017-08-03 14:14:22 -0700 |
|---|---|---|
| committer | Johnathan Corgan <johnathan@corganlabs.com> | 2017-08-03 14:14:22 -0700 |
| commit | dea13b30e411b5239c39dd63bc13f5344c945701 (patch) | |
| tree | b8b033c7f12847f117d8b6283ba2797c3e8d3312 /docs/doxygen/other/operating_fg.dox | |
| parent | 3b3a403e8871bdb83f8cd9bdc904626de14a7cca (diff) | |
| parent | 3aae388352bd78f48cbe75efab989187fee271bb (diff) | |
Merge branch 'maint'
Diffstat (limited to 'docs/doxygen/other/operating_fg.dox')
| -rw-r--r-- | docs/doxygen/other/operating_fg.dox | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/doxygen/other/operating_fg.dox b/docs/doxygen/other/operating_fg.dox index c2c66cccd9..62cc56fd4e 100644 --- a/docs/doxygen/other/operating_fg.dox +++ b/docs/doxygen/other/operating_fg.dox @@ -22,7 +22,7 @@ between. A program must at least create a GNU Radio 'top_block', which represents the top-most structure of the flowgraph. The top blocks provide the overall control and hold methods such as 'start,' 'stop,' -and 'wait.' +and 'wait'. The general construction of a GNU Radio application is to create a gr_top_block, instantiate the blocks, connect the blocks together, and @@ -67,7 +67,7 @@ By default, GNU Radio runs a scheduler that attempts to optimize throughput. Using a dynamic scheduler, blocks in a flowgraph pass chunks of items from sources to sinks. The sizes of these chunks will vary depending on the speed of processing. For each block, the number -of items is can process is dependent on how much space it has in its +of items it can process is dependent on how much space it has in its output buffer(s) and how many items are available on the input buffer(s). @@ -153,8 +153,8 @@ latency. Limiting the size of the buffer may decrease performance. 4. The real buffer size is actually based on a minimum granularity of the system. Typically, this is a page size, which is typically 4096 bytes. This means that any buffer size that is specified with this -command will get rounded up to the nearest granularity (e.g., page) -size. When calling max_output_buffer(port) after the flowgraph is +command will get rounded up to the nearest granularity (e.g., page size). +When calling max_output_buffer(port) after the flowgraph is started, you will get how many items were actually allocated in the buffer, which may be different than what was initially specified. |