summaryrefslogtreecommitdiffstats
path: root/tests/use_count
Commit message (Collapse)AuthorAgeFilesLines
* Check for osmo_fsm_register() error return valueHarald Welte2019-12-011-1/+1
| | | | Change-Id: Idbc1557739b2a253b73914e6f1f18a6d169d882e
* add osmo_use_count APINeels Hofmeyr2019-04-083-0/+510
Provide a common implementation of use counting that supports naming each user as well as counting more than just one use per user, depending on the rules the caller implies. In osmo-msc, we were originally using a simple int counter to see whether a connection is still in use or should be discarded. For clarity, we later added names to each user in the form of a bitmask of flags, to figure out exactly which users are still active: for logging and to debug double get / double put bugs. This however is still not adequate, since there may be more than one CM Service Request pending. Also, it is a specialized implementation that is not re-usable. With this generalized implementation, we can: - fix the problem of inadequate counting of multiple concurrent CM Service Requests (more than one use count per user category), - directly use arbitrary names for uses like __func__ or "foo" (no need to define enums and value_string[]s), - re-use the same code for e.g. vlr_subscr and get fairly detailed VLR susbscriber usage logging for free. Change-Id: Ife31e6798b4e728a23913179e346552a7dd338c0