;
>>
>>
>> “elog trace dispatch”
>>
>> “event-logger save ”
>>
>>
>>
>> Refer to this page to see how to view the resulting event log file:
>> https://fd.io/docs/vpp/master/gettingstarted/developers/eventviewer.html
>>
>>
>&g
t;
>
>
> *From:* Nagaraju Vemuri
> *Sent:* Friday, March 27, 2020 4:41 PM
> *To:* Dave Barach (dbarach)
> *Subject:* Re: [vpp-dev] clocks stored in vlib_node_runtime_t #vpp
> #counters
>
>
>
> We are registering a node, where we do little heavy file ope
: Re: [vpp-dev] clocks stored in vlib_node_runtime_t #vpp #counters
We are registering a node, where we do little heavy file operations and it is
taking 2.5sec or so.
We are going to fix it.
This infra is supposed to catch any such wrongly coded node.
If max_clock logic is wrong, we will never
ode_runtime_update_stats(...)
>
>
>
> *From:* Nagaraju Vemuri
> *Sent:* Friday, March 27, 2020 12:54 PM
> *To:* Dave Barach (dbarach)
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] clocks stored in vlib_node_runtime_t #vpp
> #counters
>
>
>
> Thanks for you
vlib_node_runtime_update_stats(...)
From: Nagaraju Vemuri
Sent: Friday, March 27, 2020 12:54 PM
To: Dave Barach (dbarach)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] clocks stored in vlib_node_runtime_t #vpp #counters
Thanks for your reply Dave.
Can you please point me to the code where we
>
> *From:* vpp-dev@lists.fd.io *On Behalf Of *
> nagarajuiit...@gmail.com
> *Sent:* Friday, March 27, 2020 1:59 AM
> *To:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] clocks stored in vlib_node_runtime_t #vpp #counters
>
>
>
> Hi,
>
> I see that clib_cpu_time_no
@lists.fd.io On Behalf Of
nagarajuiit...@gmail.com
Sent: Friday, March 27, 2020 1:59 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] clocks stored in vlib_node_runtime_t #vpp #counters
Hi,
I see that clib_cpu_time_now() returns u64 type data.
And we are updating max clocks spent by a node
Hi,
I see that clib_cpu_time_now() returns u64 type data.
And we are updating max clocks spent by a node in vlib_node_runtime_t using
these timestamps.
Why are we using u32 types in vlib_node_runtime_t?
Because of this, it can only hold data within 2 seconds and anything above 32
bit range
