Either protect the data structures with a clib_spin_lock, or switch to per-thread policer pools.
The config pool might as well stay on the main thread, with it and the related name-to-index hash table protected by a spinlock. Patches welcome, after the 19.08 RC1 throttle-pull is complete. Please don’t modify the binary API messages, as opposed to message handlers. D. From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Satya Murthy Sent: Wednesday, August 7, 2019 10:24 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] Is VPP vnet policer thread safe Hi , Would like to know if vnet policer is thread safe or not. To be more specific: can multiple WORKER threads (not main thread) add vnet policers at the same time without any issues ? In contrast to the "main" thread adding the policers via vpp-api, the "worker" threads add the policers due to some constraints in our architecture. -- Thanks & Regards, Murthy
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13680): https://lists.fd.io/g/vpp-dev/message/13680 Mute This Topic: https://lists.fd.io/mt/32782772/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
