Hi Murthy, Glad it helps! By construction, when vcl is initialized (vppcom_app_create()) only one worker is initialized. As long as you don’t register other workers (vppcom_worker_register), you don’t really have to worry about anything else and there are no performance penalties.
It’s important to remember that vcl is not thread safe by itself, i.e., workers will never take any locks exactly because we want them to be as light weight as possible. If the application does not want to manage locking/forking, it should use vcl_locked (vls) but that’s an entirely different topic. Regards, Florin > On Mar 13, 2020, at 9:49 AM, Satya Murthy <satyamurthy1...@gmail.com> wrote: > > Hi Florin, > > Thanks a lot for the detailed explanation. This kind of gives an overview of > this area, which really helps in our integration. > > Just one more question: > We are planning to remove the concept of vcl worker in our worker, as our app > is a single threaded app and will not be multi-threaded at any point of time > in future as well. Hope this is doable and does not pose any restrictions in > any of the VCL s/w layers. > > -- > Thanks & Regards, > Murthy
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15781): https://lists.fd.io/g/vpp-dev/message/15781 Mute This Topic: https://lists.fd.io/mt/71899986/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
