[vpp-dev] vapi stuck after vpp restart. #vapi

Hi Everyone! My client application use vapi to connect to vpp. When vpp restarts, my application gets stuck at the vapi call. When I also restart my application, everything becomes normal. *I guess this is due to a broken connection.* Is there a way to reconnect without restarting my application? A

Re: [vpp-dev] using vpp with iperf3

Hi, If you want to run iperf3 through VPP’s host stack, please use [1]. Two vpp instances are enough for the test. Regards, Florin [1] https://wiki.fd.io/view/VPP/HostStack/LDP/iperf > On Jul 7, 2020, at 7:54 AM, sadhanakesa...@gmail.com wrote: > > Hi Team, > i am trying to follow this >

[vpp-dev] using vpp with iperf3

Hi Team, i am trying to follow this documentation: https://fd.io/docs/vpp/master/usecases/simpleperf/iperf31.html on vpp with iperf3 . 1. I can see 2 graph nodes additionally tcp4-input , tcp4-reset - are this executing tcp connection in user space? 2. can this documentation performed with just

Re: [vpp-dev] Query on Performance with pools

“perf top -p `pidof vpp`” and go figure out what’s happening. Drill down on your node dispatch function, and look for stalls. What you’re describing sounds like a non-functional prefetch strategy or other coding error. Since we can’t look at the code, that’s about all we have to suggest... Dav

[vpp-dev] Query on Performance with pools

Hi , We are seeing following observations when we do performance tests with our plugin/graphnodes. 1. When we have 1 subscriber session, our custom-graph-node takes 1.35e1 cycles  ( 60 vec/call ) 2. When we have 200 subscriber sessions, the same custom-graph-node takes 1.2e2 cycles ( same 60 v

Re: [vpp-dev]: ASSERT in load_balance_get()

Hi Benoit, I have all those fixes. I had reported this issue (27407), the others i found during my tests and added barrier protection in all those places. This ASSERT seems to be not due to pool expansion, as what I have seen mostly in those cases is an invalid pointer access causing a SIGSEGV. He

Re: [vpp-dev] VPP gerrit build failing on master branch

Hmm I do not see any obvious error. I just check in a fresh Ubuntu 18.04 container and it worked flawlessly: ~# git clone https://gerrit.fd.io/r/vpp ~# make install-dep ~# make build I'd advise you start again from a fresh checkout directory, something must have gone wrong. Best ben > -Origi

Re: [vpp-dev] VPP gerrit build failing on master branch

Please find attached nasm.build.log, nasm.config.log and nasm.install.log. Thanks and Regards, Chinmaya Agarwal nasm.build.log Description: Binary data nasm.config.log Description: Binary data nasm.install.log Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages s

Re: [vpp-dev] VPP gerrit build failing on master branch

Hi, > Execution of "make install-ext-dep" is giving the same error : - Can you share the content of /root/vpp/build/external/deb/_build/nasm.*.log ? Thanks ben -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16901): https://lists.fd.io/g/vpp-dev/m

Re: [vpp-dev] VPP gerrit build failing on master branch

Execution of " make install-ext-dep " is giving the same error : - root@ggnlabvm-hnsnfvsdn03:~/vpp# make install-ext-dep make -C build/external install-deb make[1]: Entering directory '/root/vpp/build/external' make[2]: Entering directory '/root/vpp/build/external' dpkg-buildpackage: info: source

Re: [vpp-dev]: ASSERT in load_balance_get()

Hi Rajith, You are probably missing https://gerrit.fd.io/r/c/vpp/+/27407 https://gerrit.fd.io/r/c/vpp/+/27454 and maybe https://gerrit.fd.io/r/c/vpp/+/27448 Best ben > -Original Message- > From: vpp-dev@lists.fd.io On Behalf Of Rajith PR via > lists.fd.io > Sent: mardi 7 juillet 2020

Re: [vpp-dev] VPP gerrit build failing on master branch

Hi, We are missing logs prior to those to fully understand what is going on, but the build system is supposed to compile nasm prior to ipsec-mb and something went wrong. Maybe a look to /root/vpp/build-root/build-vpp_debug-native/external/nasm.build.log can help. Other than that, you should pro

[vpp-dev]: ASSERT in load_balance_get()

Hi All, During our scale testing of routes we have hit an ASSERT in *load_balance_get() . * From the code it looks like the lb_index(148) referred to is already returned to the pool by the main thread causing the ASSERT in the worker. The version in *19.08. *We have two workers and a main thread.

[vpp-dev] VPP gerrit build failing on master branch

Hi, I cloned the VPP gerrit repository on my Ubuntu 18 machine. Execution of "make install-dep" works fine but on executing "make build" , I am getting following error :- --- building ipsec-mb 0.53 - log: /root/vpp/build-root/build-vpp_debug-native/external/ipsec-mb.build.log make[4]: /root/vpp

[vpp-dev] VPP Gerrit Building failing on master branch

Hi, I cloned the VPP gerrit repository on my Ubuntu 18 machine. Execution of "make install-dep" works fine but on executing "make build" , I am getting following error :- --- building ipsec-mb 0.53 - log: /root/vpp/build-root/build-vpp_debug-native/external/ipsec-mb.build.log make[4]: /root/vpp

[vpp-dev] IOAM with IPv4 classification #vpp #vnet #classify

Hi, Is there an example where we can add telemetry data to IPv4 packets?  I've only seen IPv6 by adding the hop-by-hop header.  Is something like this possible for IPv4? Thanks, Mauricio -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16894): htt

Re: [vpp-dev] VPP20.01: vpp-20.01/src/vnet/session/application.c:960 (vnet_listen) assertion `vlib_thread_is_main_w_barrier ()' fails

Hi Florin, Thanks a lot for the input. Tried your suggestion and it looks good. One query: Is this applicable to "vnet_connect_uri" api as well? I.e it shall be called from main thread? Regards, Aishwarya -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Onl

[vpp-dev] ASSERT in load_balance_get()

Hi All, During our scale testing of routes we have hit an ASSERT in *load_balance_get() . * From the code it looks like the lb_index(148) referred to is already returned to the pool by the main thread causing the ASSERT in the worker. The version in *19.08. *We have two workers and a main thread.