path: root/src/common/vty.c
diff options
authorHarald Welte <laforge@gnumonks.org>2019-06-02 17:36:21 +0200
committerlaforge <laforge@gnumonks.org>2019-06-13 15:37:13 +0000
commitb24ef2357032c1ed25c2f95f8ca2e7b4cd013e82 (patch)
tree1b0f8a5eda17b1636e027e60db4b771c12684f22 /src/common/vty.c
parent01c539284e85c5d907300e45548d497cca27217b (diff)
l1sap: Compute statistics on FN advance in PH-RTS.ind
Let's keep some statistics about the min/max/average frame number advance that we're observing above L1SAP when comparing the time in the PH-RTS.ind and the frame number we observe in PH-DATA.ind of data that was received on the uplink. The statistics are currently only shown in the VTY, but this is a precursor to using them to correctly advance the LAPDm timers in a follow-up patch. Change-Id: I8f739fdb808a614f080afbc4654641ec3df19eb2 Related: OS#2294 Related: OS#3906
Diffstat (limited to 'src/common/vty.c')
1 files changed, 2 insertions, 0 deletions
diff --git a/src/common/vty.c b/src/common/vty.c
index 1d25bfb5..f4fc1815 100644
--- a/src/common/vty.c
+++ b/src/common/vty.c
@@ -895,6 +895,8 @@ static void bts_dump_vty(struct vty *vty, struct gsm_bts *bts)
vty_out(vty, " OML Link state: %s.%s",
bts->oml_link ? "connected" : "disconnected", VTY_NEWLINE);
+ vty_out(vty, " PH-RTS.ind FN advance average: %d, min: %d, max: %d%s",
+ bts_get_avg_fn_advance(bts), bts->fn_stats.min, bts->fn_stats.max, VTY_NEWLINE);
llist_for_each_entry(trx, &bts->trx_list, list) {
struct phy_instance *pinst = trx_phy_instance(trx);