discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Re: double buffering with new thread-per-block sc


From: Eric Blossom
Subject: Re: [Discuss-gnuradio] Re: double buffering with new thread-per-block scheduler
Date: Wed, 3 Sep 2008 17:36:06 -0700
User-agent: Mutt/1.5.17 (2007-11-01)

On Thu, Sep 04, 2008 at 01:12:26AM +0300, Juha Vierinen wrote:
> Responding to my own mail. It seems that you cannot have two disjoint
> parts within a graph.

This is incorrect.

See for example the "single argument version of connect" such as used
in gnuradio-examples/python/digital/tunnel.py and documented in 
gr_hier_block2.h



class my_top_block(gr.top_block):

    def __init__(self, mod_class, demod_class,
                 rx_callback, options):

        gr.top_block.__init__(self)
        self.txpath = transmit_path(mod_class, options)
        self.rxpath = receive_path(demod_class, rx_callback, options)
        self.connect(self.txpath);
        self.connect(self.rxpath);



> For now I solved the problem by increasing nblocks to an insanely large 
> number.

You could create a block that's sole purpose was to serve as your
large buffer.  It could have an arbitrarily large internal buffer (10M
samples?).  It would derive from gr_block.

By default the buffer size between each block is on the order of 64KB.

Eric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]