[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: |
Eric Blossom |
Subject: |
Re: [Discuss-gnuradio] Why does general_work return large number? |
Date: |
Thu, 10 Jun 2010 11:06:28 -0700 |
User-agent: |
Mutt/1.5.20 (2009-08-17) |
On Thu, Jun 10, 2010 at 06:35:18AM -0700, Zohair wrote:
>
> 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];
> }
>
Yes. So what? If we generated only a single output sample per call
to work, the entire system would run very much slower. As it's coded,
it produces one output sample for each input sample, for any value of
noutput_items.
Eric, de K7GNU clear.
- [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, 2010/06/10
- Re: [Discuss-gnuradio] Why does general_work return large number?,
Eric Blossom <=
- [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