> I don’t think that recv_async_msg() blocks. So an infinite loop will chews up
> CPU.
I had a separate thread that only called recv_async_msg(). I have unused cores
on my machine, my reasoning was that I’d rather have a CPU busy looping than
risk Ls on my transmit because the hot loop Tx threa
On 2022-01-03 16:36, ri28...@mit.edu wrote:
Hi Marcus,
I’ve attempted to use uhd::tx_streamer::recv_async_msg() before, but
it slowed down my application and caused frequent lates on the
tx_streamer. I’m unclear on the intended usage. I tried creating a
separate thread that polls in an infi
I don’t think that recv_async_msg() blocks. So an infinite loop will chews up
CPU.
The production o O/L/D/U happens independently. I’m struggling with multi
laptop failure right now or I’d get you more info on shutting those off. I
assume that redirection is not appropriate because your applic
Hi Marcus,
I’ve attempted to use uhd::tx_streamer::recv_async_msg() before, but it slowed
down my application and caused frequent lates on the tx_streamer. I’m unclear
on the intended usage. I tried creating a separate thread that polls in an
infinite while loop looking for async messages. Am I
On 2022-01-03 14:16, Richard Joseph Muri wrote:
Hello,
I have a Linux C++ application using UHD 3.13 and an x310 USRP.
Occasionally my host machine sends a late packet to the USRP,
resulting in UHD printing an “L” to stdout, or the host machine drops
some packets, resulting in UHD printing a
