Makes sense now. Thanks Dave.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14023): https://lists.fd.io/g/vpp-dev/message/14023
Mute This Topic: https://lists.fd.io/mt/34196878/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists
Each thread has its own vlib_main_t.
From: vpp-dev@lists.fd.io On Behalf Of Vamsi Krishna
Sent: Thursday, September 19, 2019 7:51 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Can vlib_time_now be used in worker threads
Hi Damjan,
I was going through the following code which vlib_time_now
Hi Damjan,
I was going through the following code which vlib_time_now calls internally.
This function takes 'c' as an input which is the timing context and
vlib_time_now passes a reference to global timing context in vlib_main.
If multiple threads call the function at the same time then it can r
> On 19 Sep 2019, at 07:42, Vamsi Krishna wrote:
>
> Hi,
>
> Can the vlib_time_now api be used in worker threads? Looking at the code,
> this api does not seam to be thread safe.
> But there are a few places where it is used in nodes that do packet
> processing. For example in nat, cdp and f
Hi,
Can the vlib_time_now api be used in worker threads? Looking at the code, this
api does not seam to be thread safe.
But there are a few places where it is used in nodes that do packet processing.
For example in nat, cdp and few other places.
Found the following thread where it is mentioned
