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 > On 25 Sep 2019, at 08:24, Satya Murthy <satyamurthy1...@gmail.com> wrote: > > 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 vpp main_thread for add/del. > Also, this list will be accessed by worker thread during packet processing. > > So, is this list guarded by any lock at lower layers for synchronizing the > access between main thread and worker thread ? > > Thanks & Regards, > Satish > > > -- > Thanks & Regards, > Murthy > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#14049): https://lists.fd.io/g/vpp-dev/message/14049 > Mute This Topic: https://lists.fd.io/mt/34285184/675608 > Group Owner: vpp-dev+ow...@lists.fd.io > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [ayour...@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14050): https://lists.fd.io/g/vpp-dev/message/14050 Mute This Topic: https://lists.fd.io/mt/34285184/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
