Hi Satya, VCL is a library applications can link against to interact with vpp’s host stack in a way similar to but not quite POSIX compliant. That is, it can be used to open sessions with various transports (e.g., tcp, quic, tls) to send/receive data in a synchronous and asynchronous manner. The exchange of data and notifications between vpp and vcl is done using shared memory, but everything is organized around sessions which in vpp are associated to worker threads.
In theory, you could imagine your control plane app listening on a given tcp port and then writing a vpp builtin application (see [1]) that tcp connects on all workers to the control plane session. These per-worker sessions are what you’re looking for at point 3 and their buffers (we call them fifos) can be larger than 1MB. However, ultimately, this leads to writing an input node for the builtin app where the workers read the messages the control plane app sent on each session and react to it. So, I’m not sure it’s worth using all of this infra instead of just writing your custom one. I guess it depends on what you need to achieve. More info on the host stack here [2]. You probably want to check the presentation at the end [3]. Regards, Florin [1] https://git.fd.io/vpp/tree/src/plugins/hs_apps/echo_client.c <https://git.fd.io/vpp/tree/src/plugins/hs_apps/echo_client.c> [2] https://wiki.fd.io/view/VPP/HostStack <https://wiki.fd.io/view/VPP/HostStack> [3] https://wiki.fd.io/images/9/9c/Vpp-hoststack-kc-eu19.pdf <https://wiki.fd.io/images/9/9c/Vpp-hoststack-kc-eu19.pdf> > On Jan 6, 2020, at 2:05 AM, Satya Murthy <satyamurthy1...@gmail.com> wrote: > > Hi , > > Have one basic doubt on applicability of VppCom library for a use case that > we have as below. > > Use Case with following requirements: > 1. control plane app needs to communicate with different VPP worker threads > 2. control plane app may need to send messages to vpp workers with message > size that can span upto a max size of 1 MB. > 3. control plane app needs to have different VppCom channels with each worker > > For the above scenario, is VppCom a suitable infrastructure ? > Using memif causes max size limit at 64KB. Hence, we are thinking about > alternatives. > > Please share your inputs on this. > ( Also, is there any documentation on VppCom library ? ) > > -- > Thanks & Regards, > Murthy -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#15056): https://lists.fd.io/g/vpp-dev/message/15056 > Mute This Topic: https://lists.fd.io/mt/69461619/675152 > Group Owner: vpp-dev+ow...@lists.fd.io > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [fcoras.li...@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15064): https://lists.fd.io/g/vpp-dev/message/15064 Mute This Topic: https://lists.fd.io/mt/69461619/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
