> On 14 Nov 2020, at 00:44, Christian Hopps <cho...@chopps.org> wrote: > > Yeah, I ended up doing this. Would be nice to have access to a "double" vs > "u64" type, but using vlib_set_counter works well enough for me.
>From the perspective of the stat infra it doesn’t much matter. As long as it’s >64 bit aligned and updated atomically. Cheers Ole > > Thanks, > Chris. > >> On Nov 13, 2020, at 5:16 PM, otr...@employees.org wrote: >> >> Hi Christian, >> >> Aboslutely. The periodic gauge callback is purely there for sources that >> don't provide the counters themselves. >> E.g. used for polling mempry heaps, free buffers and so on. >> >> You can just use a normal counter (counter.c) for your high frequency gauge. >> >> Cheers, >> Ole >> >>>> On 13 Nov 2020, at 20:20, Christian Hopps <cho...@chopps.org> wrote: >>> >>> I have need to track a frequently updated value (pps rate during congestion >>> control), but I need this to be close to very frequently updated (basically >>> whenever I change the value which is based on RTT). It seems the current >>> gauge code you supply a callback which updates the counter (at a default of >>> every 10 seconds). >>> >>> Is there something about the scalar stat that's different from the counter >>> stat that requires this infrequent updating? Is it possible to "register" a >>> scalar state that I can update very frequently instead directly (instead of >>> supplying a callback)? >>> >>> Thanks, >>> Chris. >>> >>> >>> >> > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18030): https://lists.fd.io/g/vpp-dev/message/18030 Mute This Topic: https://lists.fd.io/mt/78237093/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
