git grep ‘!am->is_mp_safe’
--a
> On 25 Sep 2019, at 10:24, Satya Murthy wrote:
>
> Thanks Andrew for the quick reply.
> Can you please point me to the code where the barrier lock is getting applied
> for acls.
>
> --
> Thanks & Regards,
> Murthy
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive
Thanks Andrew for the quick reply.
Can you please point me to the code where the barrier lock is getting applied
for acls.
--
Thanks & Regards,
Murthy
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14051): https://lists.fd.io/g/vpp-dev/message/140
Yes, ACL update messages are not marked as Mp-safe, consequently are subject to
barrier lock, thus we can use this pool in this way.
Pools are *not* thread safe, which is why for example the session pools for
reflexive acl processing are per-thread (see acl_fa_per_worker_data_t
structure).
--a
Hi ,
I have a basic question on how object pools are accessed by multiple threads in
VPP. Do we have any locks underlying that safe gaurd the object pools ?
For example:
In acl_main_t, we have a pool of acl lists as below.
*acl_list_t *acls; /* Pool of ACLs */*
This list will be populated by vp
