OK Eric. from what you've said I can understand that we cannot control noutput_items. All what we can do is return it from general_work(). It's solely for coordination issues and the runtime system takes control over it.
Thanks. Zoh Eric Blossom wrote: > > On Wed, Jun 09, 2010 at 11:57:24AM +0100, Zohair M. Abu Shaban wrote: >> >> Hi Eric, >> >> I have read what you recommended but still haven't understood what >> the significance of this number is. I have another block that >> generates a vector of 4 elements and the noutput_items is almost 1/4 >> the number of first block. Any further help please? >> >> Thanks again, >> Zohair > > The numbers are choosen by the GNU Radio runtime system. They may > vary over time and are dependent on the amount of buffer space > allocated by the runtime and the rates of production upstream and > consumption downstream. The values are choosen by a heuristic > designed to optimized throughput. > > If your block is properly written, it will respond appropriately to > any value of noutput_items. > > I'm not sure that I've answered your real question. I suspect that > you may be somewhat unclear about the nature of the streaming data > flow model that's used in GNU Radio. > > Eric > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > -- View this message in context: http://old.nabble.com/Why-does-general_work-return-large-number--tp28789377p28841275.html Sent from the GnuRadio mailing list archive at Nabble.com. _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
