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/.
laforge gerrit-no-reply at lists.osmocom.orglaforge 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: > Well maybe then the question is why are you using rate_ctr and not stat_items here, it really confuses me. At least at first sight, I agree. The resulting metric computed by this new code base renders a single value which matches better a state_item than a rate_ctr. Any particular argument to go for rate_ctr, Neels? > But my understanding here is that allAvailableSDCCHAllocated fits with a stat_item, which is simply a counter value changing over time. So I'm not really following on why you need all this infrastructure sorry, this all looks super complicated for no reason (I'm able to see). Maybe someone else can also shed some light on it. I guess the point is the definition of allAvailableSDCCHAllocated in TS 52.402: "This measurement provides the accumulated time during the granularity period when all available SDCCHs are in use or otherwise unavailable to be allocated." So it is not an instantaneous value of how many SDCCH are currently allocated, but actually accumulated time, as (I presume) neels' patch implements. So the question remains: Should the result be exposed as rate_ctr or as stat_item? -- 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: Sun, 31 Oct 2021 08:00:01 +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/20211031/095eafa6/attachment.htm>