Hi Ravi,
VCL is not part of the vpp app/process, it’s a library that applications can
link against to be able to interact with the session layer in a more posix-like
manner. So if your app needs a binary api connection to vpp, it needs to set it
up independent of vcl.
With regard to the “vpe
Hi Florin,
Thanks for your response, however I have a question, If I want to use another
Binary API initialization do we need to do at our Application or in VPP code.
When I check VPP source code, the initialization always with "vpe-api"
vpe_api_init calls always vl_set_memory_region_name ("/vpe-a
Looks like a corrupt binary API segment heap to me. Signal 7 in
mspace_malloc(...) is the root cause. The thread hangs due to recursion on the
mspace lock trying to print / syslog from the signal handler.
It is abnormal to allocate memory in vl_msg_api_alloc[_as_if_client] in the
first pla
Hi Eyle,
Networking-vpp 20.05.1 ought to work fine with VPP 20.09. Please do give VPP
20.09 a try in your lab testbed at least to see if it solves the problem.
--
Onong
From: on behalf of Eyle Brinkhuis
Date: Wednesday, 2 December 2020 at 9:43 PM
To: "Benoit Ganne (bganne)"
Cc: "vpp-dev@list
Hi All,
We have hit a VPP Worker Thread Deadlock issue. And from the call stacks it
looks like the main thread is waiting for workers to come back to their
main loop( ie has taken the barrier lock) and one of the two workers is on
spin lock to make an rpc to the main thread.
I believe this lock is
I can’t see how that could help as this is not a fragmented packet … ?
Thanks,
Klement
> On 2 Dec 2020, at 23:57, Mrityunjay Kumar wrote:
>
> Guys, I am not sure , my input is helpful or not but the same issue was
> triggered to me and we concluded it in a different way.
> In your packet trac
