Change in ...osmo-trx[master]: Add rate_ctr support to store/retrieve SDR errors through VTY

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

pespin gerrit-no-reply at lists.osmocom.org
Tue Jun 4 14:23:31 UTC 2019


pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-trx/+/14167 )

Change subject: Add rate_ctr support to store/retrieve SDR errors through VTY
......................................................................


Patch Set 1:

(1 comment)

https://gerrit.osmocom.org/#/c/14167/1//COMMIT_MSG 
Commit Message:

https://gerrit.osmocom.org/#/c/14167/1//COMMIT_MSG@18 
PS1, Line 18:    device:rx_underruns:          0 (0/s 0/m 0/h 0/d) Number of Rx underruns
            :     device:rx_overruns:          0 (0/s 0/m 0/h 0/d) Number of Rx overruns
> do we have a clear definition of what those are? I think the  terminology is not entirely obvious. […]
Rx underruns exist in LimeSuite. They are generated in Streamer::ReceivePacketsLoop() during read of buffers from FPGA.
So bytes read is expected to be always a multiple of FPGA packet buffer. In case that doesn't happen, underrun is increased.

Rx overrun happens indeed because it took too much time for App to read and LimeSuite cannot write all recvd bytes to internal buffers of the stream.

Tx underflow: If for some reason not enough data is present on LimeSuite internal buffers when writing to FPGA.

Tx overflow: If not all bytes willing to be sent by LimeSuite could end up inside the FPGA (due to its buffer being too full, or amount of data willing to be set being to big).

And btw, while looking at LimeSuite code, I also found out overrun/underrun values are reset every time LMS_GetStreamStatus() are called.

I created a ticket upstream to get it documented properly: https://github.com/myriadrf/LimeSuite/issues/265



-- 
To view, visit https://gerrit.osmocom.org/c/osmo-trx/+/14167
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-trx
Gerrit-Branch: master
Gerrit-Change-Id: I78b158141697e5714d04db8b9ccc96f31f34f439
Gerrit-Change-Number: 14167
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin at sysmocom.de>
Gerrit-CC: fixeria <axilirator at gmail.com>
Gerrit-Comment-Date: Tue, 04 Jun 2019 14:23:31 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Harald Welte <laforge at gnumonks.org>
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190604/9c951d22/attachment.htm>


More information about the gerrit-log mailing list