Hi Hyong, VCL runs as part of the app process so yes, your intuition was right, vcl and vpp workers are different. Note however that the session layer also accepts attachments from vpp “builtin” applications. Those end up consuming vpp worker cpu cycles as all the signaling will happen on the worker on which a given session was allocated.
Regards, Florin > On Feb 24, 2021, at 2:03 PM, [email protected] wrote: > > Hi, > > Are the VPP worker threads, configured in the 'cpu {' section of > 'startup.conf', the same as the "workers" or "worker threads" referred to in > the context of host stack / vppcom applications? The answer seems to be no, > looking at the implementation of 'vppcom_worker_register()' but wanted to > double-check. The background is that I'm looking for ways to run a set of > application logic on packets received on an interface but do not want to be > on the critical path of the vpp packet processing and am trying to determine > if writing a multi-threaded host stack application will do the trick. > > Thanks, > --Hyong > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18801): https://lists.fd.io/g/vpp-dev/message/18801 Mute This Topic: https://lists.fd.io/mt/80888917/21656 Mute #hoststack:https://lists.fd.io/g/vpp-dev/mutehashtag/hoststack Mute #vppcom:https://lists.fd.io/g/vpp-dev/mutehashtag/vppcom Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
