Thanks Dennis, it was very explanatory indeed !
Yes I am using mutex locks. But I think 50 threads is a over kill.
Also I realized that GNU Radio has thread per block while for my application
I made 50 receiver threads. I will try doing threads for every block
instead.
For some reasons I cannot
On Wed, 2016-11-02 at 10:34 -0700, Dennis Glatting wrote:
> Finally, I haven't had any problems mixing C++ 11/14 compiled code
> with GNURadio however I strongly suggest you use the same compiler.
> On this subject, mixing compilers is generally a bad thing to do
> whether it is something like GCC-
On Wed, 2016-11-02 at 06:41 -0700, sumitstop wrote:
> Hello,
>
> I am in the process of constructing my own 802.11 receiver using C
> and UHD. I was looking at the implementation of gr-ieee 802.11.
>
> I am trying to figure out how many parallel threads it is using for
> the receiver and transmi
Yes, that's the reference that I was looking for, but didn't find that
fast :)
Borrow as much of the GNU Radio concepts as you like – but to be honest,
it'd be probably easier to just take your functionality and wrap it in
GNU Radio blocks if you want the GNU Radio runtime behaviour :)
Best rega
Ok, I got it.
Meanwhile I am very optimistic to understand how GNU Radio deals with
threading and burrow some of those concepts in my framework using pthreads
:)
Is the following presentation by Tom is good to start with ?
http://www.trondeau.com/blog/2013/9/15/explaining-the-gnu-radio-schedule
At least one. I don't have the full gr-ieee802-11 architecture in my
head; some of the blocks might, as explained, be hierarchical and
contain multiple blocks.
Really, you say your software is crashing. That doesn't happen because
you have too many threads – that's because you've got some bug, and
Marcus, please correct if my understanding is wrong in the following :
If a rx is something like this :
[preamble search] -> [frame alignment] --> [deinterleaver] --> [decoder]
--> [descrambler]
So with GNU Radio framework there will one thread for each of the [ ]
bracketed component ?
-
Ok, I went thru the paper briefly, so it seems that GNU Radio takes care of
the threads for all the blocks.
"By default GNU Radio starts one thread for every block in the flow graph."
I need to investigate if I am doing overkill by initiating 50 threads for my
receiver block !
I am making dot
ss-gnuradio
> on behalf of
> sumitstop
> *Sent:* Wednesday, November 2, 2016 9:41:48 AM
> *To:* Discuss-gnuradio@gnu.org
> *Subject:* [Discuss-gnuradio] gr-ieee 802.11 and threads for real time
>
> Hello,
>
> I am in the process of constructing my own 802.11 receive
ko Dressler
From: Discuss-gnuradio on
behalf of sumitstop
Sent: Wednesday, November 2, 2016 9:41:48 AM
To: Discuss-gnuradio@gnu.org
Subject: [Discuss-gnuradio] gr-ieee 802.11 and threads for real time
Hello,
I am in the process of constructing my own 802.11 receiver using C and
Hello,
I am in the process of constructing my own 802.11 receiver using C and UHD.
I was looking at the implementation of gr-ieee 802.11.
I am trying to figure out how many parallel threads it is using for the
receiver and transmitter. In order to work in real time, especially decoding
802.11 pa
11 matches
Mail list logo
