operation]
> perf report
>
> That should give you a text UI that allows you to see at which points in
> operation the CPU was whenever perf looked.
> If you want to share that, an easy way would be writing the call tree to a
> file, e.g. "perf report --stdio > report.tx
;t performing well enough – as I'm currently
> assuming your approach wasn't born through an in-depth analysis, but might
> more be of a trial&error iteration?
>
> Best regards,
>
> Marcus
>
> On 02.08.2017 13:10, Jack White via USRP-users wrote:
>
> Hi,
&
Hi,
I've been having some difficulty getting reliable data flow from my USRP
X310 with a GRC flowgraph, so I'm trying out writing my system in C++ with
the UHD driver API. My first step has been to retrieve samples from the
X310, forward them to a UDP port and then pick them up with a GRC Socket
P
