On 2022-02-24 09:27, page wrote:
I have seen the "stuck" behavior, although it was about a year ago and
I doubt I could reproduce it again. It occurred as I streamed two Rx
inputs at 20 MSPS on a B210 to a Raspberry Pi 4 USB 3.0. It was model
v1.1, which has known issues in the hardware impleme
I have seen the "stuck" behavior, although it was about a year ago and I doubt
I could reproduce it again. It occurred as I streamed two Rx inputs at 20 MSPS
on a B210 to a Raspberry Pi 4 USB 3.0. It was model v1.1, which has known
issues in the hardware implementation of USB 3.0. The pi is up t
On 2022-02-23 14:04, Brian Padalino wrote:
While this may be true in general, the test case is said to be (USRP
Source -> Null Sink). This is the most trivial case and should
basically be the exact same as what benchmark_rate is running, and yet
GNU Radio has overflow whereas benchmark_rate
On Wed, Feb 23, 2022 at 2:04 PM Brian Padalino wrote:
> On Wed, Feb 23, 2022 at 1:03 PM Marcus D. Leech
> wrote:
>
>> On 2022-02-23 12:00, zlika_...@hotmail.com wrote:
>> >
>> > Thanks for your answer.
>> >
>> > I tried to use benchmark_rate, and I don’t have any sample loss at
>> > 200MS/s.
>>
On Wed, Feb 23, 2022 at 1:03 PM Marcus D. Leech
wrote:
> On 2022-02-23 12:00, zlika_...@hotmail.com wrote:
> >
> > Thanks for your answer.
> >
> > I tried to use benchmark_rate, and I don’t have any sample loss at
> > 200MS/s.
> >
> > On GnuRadio with a very simple flowgraph (USRP Source -> Null
On 2022-02-23 12:00, zlika_...@hotmail.com wrote:
Thanks for your answer.
I tried to use benchmark_rate, and I don’t have any sample loss at
200MS/s.
On GnuRadio with a very simple flowgraph (USRP Source -> Null Sink) I
still have very regular (every few seconds) overflows.
In both cases,
Thanks for your answer.
I tried to use benchmark_rate, and I don’t have any sample loss at 200MS/s.
On GnuRadio with a very simple flowgraph (USRP Source -> Null Sink) I still
have very regular (every few seconds) overflows.
In both cases, the CPU load of each core never goes over \~25%.
Is th
On 2022-02-23 10:21, Rob Kossler wrote:
Hi Thomas,
I confess to not fully understanding the network-based back pressure.
Based on my own experience, it seems that it is possible to get either
"O" or "S/D" (despite the information mentioned at the link you
provided which indicates no back press
Hi Thomas,
I confess to not fully understanding the network-based back pressure. Based
on my own experience, it seems that it is possible to get either "O" or
"S/D" (despite the information mentioned at the link you provided which
indicates no back pressure). I would even say that "O" is more comm
