# Really need suggestions for operating on big blocks of data

**URL:** <https://www.ruby-forum.com/t/really-need-suggestions-for-operating-on-big-blocks-of-data/105314>\
**Category:** GNU Radio\
**Created:** [May 28, 2007, 7:31pm UTC](https://www.ruby-forum.com/t/really-need-suggestions-for-operating-on-big-blocks-of-data/105314 "2007-05-28T19:31:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vincenzo\_P](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/e274bd/32.png) [@Vincenzo\_P](https://www.ruby-forum.com/u/Vincenzo_P)\
**Post date:** [May 28, 2007, 7:31pm UTC](https://www.ruby-forum.com/t/really-need-suggestions-for-operating-on-big-blocks-of-data/105314/1 "2007-05-28T19:31:52Z")

</div>

sorry Eric,

I really haven’t found a proper way to operate (actually to do  
interleaving) on blocks of 6048 items of one byte, as requested by the  
standard I’m trying to implement.

maybe this is because it’s not very clear to me which way the function  
work is called at runtime and how the value of noutput\_items is  
assigned.

please, I’m really in need of some help, because what I’ve written so  
far really seems to produce decent output, but I’m stuck on my  
interleaver block.

i think that there’s somenthing on gnuradio architecture that I have  
misunderstood…

I hope you can give me some suggestions or point me towards some code  
that already operates on such big blocks…

thanks  
best regards

vincenzo

---

<div class="post-metadata">

**Author:** ![Vincenzo\_P](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/e274bd/32.png) [@Vincenzo\_P](https://www.ruby-forum.com/u/Vincenzo_P)\
**Post date:** [May 29, 2007, 5:19pm UTC](https://www.ruby-forum.com/t/really-need-suggestions-for-operating-on-big-blocks-of-data/105314/2 "2007-05-29T17:19:48Z")

</div>

On Mon, May 28, 2007 at 07:30:08PM +0200, Vincenzo P. wrote:

> please, I’m really in need of some help, because what I’ve written so  
> best regards
> 
> vincenzo

Vincenzo,

You may need to write your block based on gr\_block, and implement  
general\_work. Doing that, you will be able to (have to) manage all  
intermediate state yourself. You should accept the default  
output\_multiple (which is 1) and accept all available input. When  
you’ve got a full interleaved block ready for output, produce it,  
otherwise produce 0 output, but consume the input, and accrue your  
internal interleaver state.

Eric
