Change in osmo-bsc[master]: add time_cc API: cumlative counter for time, reported as rate_ctr

[neels]

neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/25973 )

Change subject: add time_cc API: cumlative counter for time, reported as rate_ctr
......................................................................


Patch Set 1:

> IIUC what's needed is an stat_item, a "struct timepsec start" storing the last date, and some time function setting the stat_item to timespecsub(now(),start). And setting start to {0,0} to set it to zero or keep last value or whatever. Am I missing something here?

The situation, that all channels are allocated, often fluctuates rapidly.
A channel is released, flag goes false. That last free channel is allocated again, flag goes true.

In order to determine how much time exactly all channels were allocated, you can't just remember a point in time and report the difference.

This code remembers when the flag went true and counts the time until it goes false.
Repeat that, and this code sums up those times where the flag was true.
Sounds like that is what you are trying to describe with the timespec start?


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

Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Icdd36f27cb54b2e1b940c9e6404ba9dd3692a310
Gerrit-Change-Number: 25973
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge at osmocom.org>
Gerrit-CC: pespin <pespin at sysmocom.de>
Gerrit-Comment-Date: Tue, 02 Nov 2021 16:29:11 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20211102/9325ec51/attachment.htm>