[vpp-dev] network loop

Hi all, My version is 17.04, sometimes there will be a large number of packets transmitted by vpp. It looks like that vpp has network loop itself. Here is the stack when the loop happened. Any idea? (gdb) c Continuing. ^C Thread 1 "vpp_main" received signal SIGINT, Interrupt.

Re: [vpp-dev] [csit-dev] vpp continuous integration on armv8

If I understand this correctly, Tina wants these Arm machines to be used as build/HW validation. I am cc-ing our folks in Huawei, who are going to work in the community on CSIT to see if they can provide any help, contact person would be Appana Prasad and Khemendra Kumar. Thanks, George

Re: [vpp-dev] [csit-dev] vpp continuous integration on armv8

Ed, Based on Tina saying the ones delivered are OD1000’s, Overdrive machines seem to come from the factory with Suse on them according to their website. Chris. From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On Behalf Of Ed Warnicke Sent: Thursday, November 16, 2017

Re: [vpp-dev] vpp continuous integration on armv8

Dear Ed, What arrived in Canada yesterday were 3x OD1000 for build only. 3 ThunderX are still in process, waiting to be quoted, billed, and shipped, they are also for VPP build only. 3x http://b2b.gigabyte.com/ARM-Server/R150-T60-rev-110#ov Thank you, Tina Tsou Enterprise Architect Arm

Re: [vpp-dev] vpp continuous integration on armv8

Gabriel, We do need to have multiple workers to service the verify queue... having the queue back up behind a single server wouldn't be good. Do you know if these boxes are installed with Ubuntu 16.04 already? Ed On Thu, Nov 16, 2017 at 9:03 AM Gabriel Ganne wrote: >

[vpp-dev] Mapping multiple FIBs from Linux to VPP

Hi, I can see in "vppsb/netlink/librtnl/mapper.h" that each Linux namespace is mapped to a separate FIB in VPP. However, the 4.6 Linux kernel has support for VRFs (e.g., using "ip link add dev NAME type vrf table ID"). If we use the second (VRFs) approach to create multiple FIBs in Linux, can

[vpp-dev] FOSDEM 2018

Folks, The Call for Content for FOSDEM 2018 is closing today! The "SDN and NFV room" at FOSDEM is great way to get the FD.io message out there. Last minute submissions would be most welcome! To submit see, https://blogs.gnome.org/bolsh/2017/11/01/fosdem-2018-sdnnfv-devroom-call-for-content/

Re: [vpp-dev] vpp continuous integration on armv8

Yes, they are. I estimate it should take about 40 minutes to build and test with 8 cores in release mode, therefore I do not think that using all 3 ThunderX is necessary. I do not have access to a ThunderX platform on my side (I ran my tests on NXP and Hierofalcon platforms), if needed please

Re: [vpp-dev] vpp continuous integration on armv8

Gabriel, This is awesome news! Do I understand correctly that these ThunderX boards are intended to be used for build/make test/packaging? If so, I've cced in Vanessa, our fearless sysadmin to help in figuring these things out :) Do you have opinions about which Linux distributions you want to

Re: [vpp-dev] Flowprobe Question

Thanks Ole, got it working after running the tests and digging through the test code. I'm able to capture and parse the IPFIX output from the Flowprobe plugin. I have another question. I'm going through the examples, specifically the "Progressive Tutorial - Source NAT" and "VPP/Configure VPP As

[vpp-dev] vpp continuous integration on armv8

Hi, We've been working on preparing vpp for armv8 continuous testing (See https://wiki.fd.io/view/VPP/AArch64), and we think that we now have everything which is required to add arm as ci platform in the vpp review process (build, test and packaging). All the test have been done on "native".

[vpp-dev] VPP as IPsec gateway with destination packets for application process on same NUMA node

Hi, We want to use VPP for terminating an IPsec tunnel, and forward the inner IP packets to another (application) process on the same NUMA node. What are the options for doing that, other than forwarding the packets through the Kernel ip stack? The application process itself is built to