Folks,
We are seeing a really strange VPP API message processing problem.
The scenario goes like this...
Our CLI issues C API calls through the vlib API. The messages hit
the shared memory queue, but are not processed. They sit there.
Later, we fire up, say, vppctl and do a "show api" command. That
causes the queue to be flushed and the first thing it does is process
the outstanding API messages from our CLI.
This used to work. About two weeks ago I started pulling in the
top-of-tree stuff to get us closer to development head and get
some of the needed bug fixes.
I'm wondering if this sounds familiar to you at all?
I've started to isolate it with git bisect, and so far I believe the
behavior changed between these commits:
$ git log --oneline
...
553a411 VPP-585: vhost-user interface deletion leaks memory.
ffc18f5 japi: include tests in jar files
738f3f2 API refactoring : dpdk
6bbf83a Revert "vppctl: bash completion for vppctl commands"
842b9c5 Self-service garbage collection for the API message allocator
d995c75 vppctl: bash completion for vppctl commands
0d3c1cc VPP-279: af_packet via Command-line Arg should no longer be
supported
48c1824 Update CSIT tests 170101 -> 170108
...
I've not had a chance to look at them yet, but of those, the most
suspicious looking one to me is:
842b9c5 Self-service garbage collection for the API message allocator
If no one beats me to it, I'll continue bisecting it tomorrow...
Thanks,
jdl
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
