Re: [vpp-dev] VPP 20.01 build error

2020-02-24 Thread Benoit Ganne (bganne) via Lists.Fd.Io
> When I give command of "make build", > I got the error (attached tail part of error) [...] > echo: I/O error TL;DR: in your shell, try to run bash (from inside your current shell, so you end up with a nested shell) and logout (return back to your original shell), then try to compile again. Th

Re: [vpp-dev] VAPI improvement?

2020-02-24 Thread Ole Troan
Hi Christian, > [from another thread] > >> - VAPI seems to require callbacks for results. [...] Having callbacks with >> synchronous calls is pretty cumbersome, is there a way around having to use >> callbacks with VAPI? > > This is actually makes vapi pretty unappealing (at least for me). >

[vpp-dev] Coverity run FAILED as of 2020-02-24 14:00:55 UTC

2020-02-24 Thread Noreply Jenkins
Coverity run failed today. Current number of outstanding issues are 1 Newly detected: 0 Eliminated: 1 More details can be found at https://scan.coverity.com/projects/fd-io-vpp/view_defects -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15509): ht

Re: [vpp-dev] Confirm your kausik.majum...@commscope.com email address

2020-02-24 Thread Majumdar, Kausik
Hi, I have subscribed to VPP dev mailing alias. Confirming my email address. Thanks, Kausik From: FD.io Sent: Monday, February 24, 2020 10:19 AM To: Majumdar, Kausik Subject: [vpp-dev] Confirm your kausik.majum...@commscope.com email address Message received from external source. Exercise ca

Re: [vpp-dev] RFC: FD.io Summit (Userspace), September, Bordeaux France

2020-02-24 Thread Honnappa Nagarahalli
> > Hi folks, > > A 2020 FD.io event is something that has been discussed a number of times > recently at the FD.io TSC. > With the possibility of co-locating such an event with DPDK Userspace, in > Bordeaux, in September. > > Clearly, we are incredibly eager to make sure that such an event wo

Re: [vpp-dev] RFC: FD.io Summit (Userspace), September, Bordeaux France

2020-02-24 Thread Luca Muscariello
A few people from the hicn/cicn projects may be able to attend in Bordeaux. Luca On Mon, Feb 24, 2020 at 7:48 PM Honnappa Nagarahalli < honnappa.nagaraha...@arm.com> wrote: > > > > > > Hi folks, > > > > A 2020 FD.io event is something that has been discussed a number of times > > recently at th

[vpp-dev] vmxnet3 rx-queue error "vmxnet3 failed to activate dev error 1" #vmxnet3 #ipsec

2020-02-24 Thread ravinder . yadav
VPP IPsec responder on ESXI VM RHEL 7.6 Is there a limitation on the number of num-tx-queues and num-rx-queues we can associate with vmxnet3? I have 12 worker threads running but when i try to associate more than 4 num-rx-queues i get error saying "vmxnet3 failed to activate dev error 1"

Re: [vpp-dev] vmxnet3 rx-queue error "vmxnet3 failed to activate dev error 1" #vmxnet3 #ipsec

2020-02-24 Thread steven luong via Lists.Fd.Io
It works for me although I am on ubuntu 1804 VM. Your statement is unclear to me if your problem is strictly related to more than 4 rx-queues or not when you say “but when i try to associate more than 4 num-rx-queues i get error” Does it work fine when you reduce the number of rx-queues less tha

Re: [vpp-dev] vmxnet3 rx-queue error "vmxnet3 failed to activate dev error 1" #vmxnet3 #ipsec

2020-02-24 Thread ravinder . yadav
Yes it works fine with num-rx-queues 4 and below. vpp# sh threads ID Name Type LWP Sched Policy (Priority) lcore Core Socket State 0 vpp_main 2726 other (0) 1 0 0 1 vpp_wk_0 workers 2730 other (0) 2 0 4 2 vpp_wk_1 workers 2731 other (0) 3 0 6 3 vpp_wk_2 workers 2732 other (0) 4 0 8 4 vpp_wk_