[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Why does general_work return large number?
From: |
Zohair |
Subject: |
Re: [Discuss-gnuradio] Why does general_work return large number? |
Date: |
Thu, 10 Jun 2010 06:35:18 -0700 (PDT) |
But again, let's go back to the howto_square example. What is the
significance of indexing the output pointer from 0 to noutput_items? This
means we are generating and storing 4096 point at a time!
float *out = (float *) output_items[0];
for (int i = 0; i < noutput_items; i++){
out[i] = in[i] * in[i];
}
Zohair wrote:
>
> 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
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/Why-does-general_work-return-large-number--tp28789377p28843219.html
Sent from the GnuRadio mailing list archive at Nabble.com.
- [Discuss-gnuradio] Why does general_work return large number?, Zohair M. Abu Shaban, 2010/06/05
- Re: [Discuss-gnuradio] Why does general_work return large number?, Eric Blossom, 2010/06/05
- RE: [Discuss-gnuradio] Why does general_work return large number?, Zohair M. Abu Shaban, 2010/06/09
- Re: [Discuss-gnuradio] Why does general_work return large number?, Eric Blossom, 2010/06/09
- Re: [Discuss-gnuradio] Why does general_work return large number?, Zohair, 2010/06/10
- Re: [Discuss-gnuradio] Why does general_work return large number?,
Zohair <=
- Re: [Discuss-gnuradio] Why does general_work return large number?, Eric Blossom, 2010/06/10
- [Discuss-gnuradio] Gnuradio/Beagleboard modifying flow graph buffer allocation, alfayez, 2010/06/10
- Re: [Discuss-gnuradio] Gnuradio/Beagleboard modifying flow graph buffer allocation, Eric Blossom, 2010/06/11
- Re: [Discuss-gnuradio] Gnuradio/Beagleboard modifying flow graph buffer allocation, Philip Balister, 2010/06/14