libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	rate_ctr: No need to include the inttypes.h	Holger Hans Peter Freyther	2010-12-20	1	-1/+0
\| \| \| \| \| \|	There should not be any u_int*_t types in this file, no need to include this file. It is breaking compilation with the last x86 build of GNU ARM for GCC 3.4.
*	[rate_ctr] always 'overflow' in next larger inetrval when interval ends	Harald Welte	2010-05-13	1	-0/+6
\| \| \| \| \| \| \| \| \| \| \|	If a second ends, we add the number of events in that just-ended second to the number of events in the currently running minute. The same happens at the end of a minute: We add the number of events in that just-ended minute into the number of events of the still-running hour, etc. This gives a much more meaningful numbers and we don't end up with "12 events per second, but 0 events per minute" kind of situations anymore.
*	rate_counters: Remove group-name-sprintf-with-idx string	Harald Welte	2010-05-13	1	-3/+0
\|
*	rate_ctr: Store the numeric index as part of 'rate_ctr_group'	Harald Welte	2010-05-13	1	-0/+1
\|
*	Add new 'rate counter' implementation to libosmocore	Harald Welte	2010-05-13	1	-0/+124
	A 'rate counter' is a counter that counts events but also keeps track of the rate of events (per second, minute, hour and day). 'rate counters' are generally abstracted in 'rate counter groups', which are instances of a 'rate counter group description'. This way we can have e.g. a description describing what kind of counters a BTS (or TRX) has - and we can then create one instance of that group for every BTS or TRX that exists.