Re: [Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-20 Thread marco Ribero
Il giorno lun 20 apr 2015 alle ore 16:30 Tom Rondeau ha scritto: > >> > We've never been hot on the idea of using VOLK for GPU stuff. VOLK kernels > tend to do one thing at a time and don't worry about data movement (too > much) because the SIMD registers are right there. Going to GPUs takes a lo

Re: [Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-20 Thread Tom Rondeau
On Mon, Apr 20, 2015 at 10:21 AM, Marcus Müller wrote: > Hi Marco, > > If I may recommend something, it would be having a look at VOLK [1]. It's > the optimizations library that comes with GNU Radio. > If you could implement some of these algorithms in CUDA, then every block > currently using VO

Re: [Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-20 Thread Marcus Müller
Hi Marco, If I may recommend something, it would be having a look at VOLK [1]. It's the optimizations library that comes with GNU Radio. If you could implement some of these algorithms in CUDA, then every block currently using VOLK (which is the majority of the arithmetically challenging blocks at

Re: [Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-20 Thread marco Ribero
I cannot do it. For my thesis,I'm trying do bring various part of GnuRadio over CUDA.. My idea is to rewrite already existing blocks with CUDA, possibly without breaking compatibility with actual implementation of gnuradio. In this way a normal user can use these blocks without problems. For the m

Re: [Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-20 Thread Marcus Müller
Hi Marco, I just realized: Things might be much more easy than that, even: What you do sounds like a job for a hierarchical block; if you're not used to that concept: It's just a "subflowgraph", represented as a block with in- and outputs. If you put both your blocks inside, you'll always have th

Re: [Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-20 Thread marco Ribero
Thank you very much. Your solution is much cleaner. Have a good day, Marco Il giorno lun 20 apr 2015 alle ore 09:29 Marcus Müller < marcus.muel...@ettus.com> ha scritto: > Hi marco, > > what you describe as ID already exist: every block has a function alias(), > giving it a string "name", which

Re: [Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-20 Thread Marcus Müller
Hi marco, what you describe as ID already exist: every block has a function alias(), giving it a string "name", which can be used with global_block_registry::block_lookup(name) [1]. You will need to wrap your alias in a pmt::intern to get it into a stream tag, so use that with block_lookup, and c

[Discuss-gnuradio] Bidirectional communication between attached blocks

2015-04-19 Thread marco Ribero
Hi all, I'd like to establish a bidirectional communication between two attached blocks, without asking the user to write code like msg_connect(). One way could be: the upstream block generate an id like ID=typeBlock+pseudorandomNumber and send it to the next block using a tag. After what the upst