Hi Ron,
I want this operating at 200 Ms/sec, so would like to avoid copying if
possible. I will look into other alternatives. Thanks, once again!
Miklos
On Tue, May 30, 2017 at 3:53 PM, Ron Economos wrote:
> AFAIK, there's no way to preserve the output buffer between general_work()
> or work()
AFAIK, there's no way to preserve the output buffer between
general_work() or work() calls. Are you that constrained with the amount
of memory your block can use? A few hundred samples is not very much. In
one of my DVB-T2 blocks, I have 786,432 bytes of static memory allocated.
https://github
Hi Ron,
Thanks for the quick response!
On Tue, May 30, 2017 at 3:32 PM, Ron Economos wrote:
> If you call set_output_multiple() in your block constructor, it will
> guarantee the size of the output buffer.
That would actually work (so I return exactly one block of items less
than requested, and
If you call set_output_multiple() in your block constructor, it will
guarantee the size of the output buffer. The scheduler won't touch it
until you exit your block with:
return noutput_items;
Ron
On 05/30/2017 12:57 PM, Miklos Maroti wrote:
Hi,
I would like to use scratch space within the
