date:20170915

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

2017-09-15 Thread Saxena, Nitin

Thanks Steven and Ruijing.


I want to try DPDK vhost with VPP v1704. Does dpdk vhost works in vpp1704? Any 
documentation on that would help.

If documentation is available for v1707 then I can switch to v1707 as well.


I am also looking for any vhost-user performance benchmark numbers on x86. Do 
we have benchmark numbers for both: VPP vhost-user and DPDK vhost?


Thanks,

Nitin


From: Steven Luong (sluong) 
Sent: Monday, September 11, 2017 7:46 PM
To: Guo, Ruijing; Saxena, Nitin; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK


If you create the VIrtualEthernet interface via the CLI or binary API, it 
always uses VPP native. If you create the virtual interface via vdev in the 
dpdk clause in the startup file, it uses dpdk’s vhost-user.



The problem is in DPDK virtio-user that they don’t comply with virtio1.0 spec. 
I submitted a patch for them. I don’t think they took it yet.



Steven



From:  on behalf of "Guo, Ruijing" 

Date: Sunday, September 10, 2017 at 5:36 PM
To: "Saxena, Nitin" , "vpp-dev@lists.fd.io" 

Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK





Just for your reference:

I am using vpp 17.07. The default one is vpp native. But it cannot work with 
virtio-user. So I change to vhost-user in dpdk.





From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Saxena, Nitin
Sent: Monday, September 11, 2017 1:22 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK



Hi All



I went through following video regarding vhost-user.



https://www.youtube.com/watch?v=z-ZRof2hDP0



The question is in this video it has been told by default VPP implementation of 
vhost-user being used and not the dpdk one. Since this video is 1 yr old and I 
am using vpp version 1704. Can anyone please comment which vhost-user code is 
by default enabled in vpp1704 - is it dpdk one or VPP native? I can see in 
vpp-master/RELEASE.md that DPDK vhost was deprecated in vpp1609? Is it fixed 
now?



Thanks,

Nitin
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

2017-09-15 Thread Saxena, Nitin

Hi,


I am more interested in DPDK vhost performance numbers. I am able to get VPP 
vhost native numbers from CSIT


Thanks,

Nitin


From: vpp-dev-boun...@lists.fd.io  on behalf of 
Saxena, Nitin 
Sent: Friday, September 15, 2017 2:10 PM
To: Steven Luong (sluong); Guo, Ruijing; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK


Thanks Steven and Ruijing.


I want to try DPDK vhost with VPP v1704. Does dpdk vhost works in vpp1704? Any 
documentation on that would help.

If documentation is available for v1707 then I can switch to v1707 as well.


I am also looking for any vhost-user performance benchmark numbers on x86. Do 
we have benchmark numbers for both: VPP vhost-user and DPDK vhost?


Thanks,

Nitin


From: Steven Luong (sluong) 
Sent: Monday, September 11, 2017 7:46 PM
To: Guo, Ruijing; Saxena, Nitin; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK


If you create the VIrtualEthernet interface via the CLI or binary API, it 
always uses VPP native. If you create the virtual interface via vdev in the 
dpdk clause in the startup file, it uses dpdk’s vhost-user.



The problem is in DPDK virtio-user that they don’t comply with virtio1.0 spec. 
I submitted a patch for them. I don’t think they took it yet.



Steven



From:  on behalf of "Guo, Ruijing" 

Date: Sunday, September 10, 2017 at 5:36 PM
To: "Saxena, Nitin" , "vpp-dev@lists.fd.io" 

Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK





Just for your reference:

I am using vpp 17.07. The default one is vpp native. But it cannot work with 
virtio-user. So I change to vhost-user in dpdk.





From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Saxena, Nitin
Sent: Monday, September 11, 2017 1:22 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK



Hi All



I went through following video regarding vhost-user.



https://www.youtube.com/watch?v=z-ZRof2hDP0



The question is in this video it has been told by default VPP implementation of 
vhost-user being used and not the dpdk one. Since this video is 1 yr old and I 
am using vpp version 1704. Can anyone please comment which vhost-user code is 
by default enabled in vpp1704 - is it dpdk one or VPP native? I can see in 
vpp-master/RELEASE.md that DPDK vhost was deprecated in vpp1609? Is it fixed 
now?



Thanks,

Nitin
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

2017-09-15 Thread Ni, Hongjun

Hi,

We also tested VPP vhost-user last week, and it did not work too.

Jianfeng Tan and I tried to locate the cause using DPDK testpmd,

And found that VPP vhost works well, but VPP virtio-user in container does not 
work.

-Hongjun

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Saxena, Nitin
Sent: Friday, September 15, 2017 6:30 PM
To: Steven Luong (sluong) ; Guo, Ruijing 
; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK


Hi,



I am more interested in DPDK vhost performance numbers. I am able to get VPP 
vhost native numbers from CSIT



Thanks,

Nitin


From: vpp-dev-boun...@lists.fd.io 
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of 
Saxena, Nitin mailto:nitin.sax...@cavium.com>>
Sent: Friday, September 15, 2017 2:10 PM
To: Steven Luong (sluong); Guo, Ruijing; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK


Thanks Steven and Ruijing.



I want to try DPDK vhost with VPP v1704. Does dpdk vhost works in vpp1704? Any 
documentation on that would help.

If documentation is available for v1707 then I can switch to v1707 as well.



I am also looking for any vhost-user performance benchmark numbers on x86. Do 
we have benchmark numbers for both: VPP vhost-user and DPDK vhost?



Thanks,

Nitin


From: Steven Luong (sluong) mailto:slu...@cisco.com>>
Sent: Monday, September 11, 2017 7:46 PM
To: Guo, Ruijing; Saxena, Nitin; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK


If you create the VIrtualEthernet interface via the CLI or binary API, it 
always uses VPP native. If you create the virtual interface via vdev in the 
dpdk clause in the startup file, it uses dpdk's vhost-user.



The problem is in DPDK virtio-user that they don't comply with virtio1.0 spec. 
I submitted a patch for them. I don't think they took it yet.



Steven



From: mailto:vpp-dev-boun...@lists.fd.io>> on 
behalf of "Guo, Ruijing" mailto:ruijing@intel.com>>
Date: Sunday, September 10, 2017 at 5:36 PM
To: "Saxena, Nitin" mailto:nitin.sax...@cavium.com>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK





Just for your reference:

I am using vpp 17.07. The default one is vpp native. But it cannot work with 
virtio-user. So I change to vhost-user in dpdk.





From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Saxena, Nitin
Sent: Monday, September 11, 2017 1:22 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK



Hi All



I went through following video regarding vhost-user.



https://www.youtube.com/watch?v=z-ZRof2hDP0



The question is in this video it has been told by default VPP implementation of 
vhost-user being used and not the dpdk one. Since this video is 1 yr old and I 
am using vpp version 1704. Can anyone please comment which vhost-user code is 
by default enabled in vpp1704 - is it dpdk one or VPP native? I can see in 
vpp-master/RELEASE.md that DPDK vhost was deprecated in vpp1609? Is it fixed 
now?



Thanks,

Nitin
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

2017-09-15 Thread Steven Luong (sluong)

From: "Saxena, Nitin" 
Date: Friday, September 15, 2017 at 1:40 AM
To: "Steven Luong (sluong)" , "Guo, Ruijing" 
, "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Thanks Steven and Ruijing.

I want to try DPDK vhost with VPP v1704. Does dpdk vhost works in vpp1704? Any 
documentation on that would help.

If documentation is available for v1707 then I can switch to v1707 as well.

 It should work. Are you trying to do

VPP with DPDK-vhost  VM

Or

VPP with DPDK vhost  VPP with DPDK virtio

I recently tested the latter on 1707. If you really want the former or 1704, I 
could try that as well.

I am also looking for any vhost-user performance benchmark numbers on x86. Do 
we have benchmark numbers for both: VPP vhost-user and DPDK vhost?

Thanks,

Nitin

From: Steven Luong (sluong) 
Sent: Monday, September 11, 2017 7:46 PM
To: Guo, Ruijing; Saxena, Nitin; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

If you create the VIrtualEthernet interface via the CLI or binary API, it 
always uses VPP native. If you create the virtual interface via vdev in the 
dpdk clause in the startup file, it uses dpdk’s vhost-user.

The problem is in DPDK virtio-user that they don’t comply with virtio1.0 spec. 
I submitted a patch for them. I don’t think they took it yet.

Steven

From:  on behalf of "Guo, Ruijing" 

Date: Sunday, September 10, 2017 at 5:36 PM
To: "Saxena, Nitin" , "vpp-dev@lists.fd.io" 

Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Just for your reference:

I am using vpp 17.07. The default one is vpp native. But it cannot work with 
virtio-user. So I change to vhost-user in dpdk.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Saxena, Nitin
Sent: Monday, September 11, 2017 1:22 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Hi All

I went through following video regarding vhost-user.

https://www.youtube.com/watch?v=z-ZRof2hDP0

The question is in this video it has been told by default VPP implementation of 
vhost-user being used and not the dpdk one. Since this video is 1 yr old and I 
am using vpp version 1704. Can anyone please comment which vhost-user code is 
by default enabled in vpp1704 - is it dpdk one or VPP native? I can see in 
vpp-master/RELEASE.md that DPDK vhost was deprecated in vpp1609? Is it fixed 
now?

Thanks,

Nitin
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

2017-09-15 Thread Steven Luong (sluong)

From: "Ni, Hongjun" 
Date: Friday, September 15, 2017 at 6:11 AM
To: "Saxena, Nitin" , "Steven Luong (sluong)" 
, "Guo, Ruijing" , 
"vpp-dev@lists.fd.io" , "Tan, Jianfeng" 

Subject: RE: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Hi,

We also tested VPP vhost-user last week, and it did not work too.

 If you try to connect VPP native vhost user with VPP DPDK virtio, you 
need a patch in DPDK. I already submitted the patch for DPDK and it is already 
applied to dpdk-next-virtio branch recently.

Steven

Jianfeng Tan and I tried to locate the cause using DPDK testpmd,

And found that VPP vhost works well, but VPP virtio-user in container does not 
work.

-Hongjun

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Saxena, Nitin
Sent: Friday, September 15, 2017 6:30 PM
To: Steven Luong (sluong) ; Guo, Ruijing 
; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Hi,

I am more interested in DPDK vhost performance numbers. I am able to get VPP 
vhost native numbers from CSIT

Thanks,

Nitin

From: vpp-dev-boun...@lists.fd.io 
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of 
Saxena, Nitin mailto:nitin.sax...@cavium.com>>
Sent: Friday, September 15, 2017 2:10 PM
To: Steven Luong (sluong); Guo, Ruijing; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Thanks Steven and Ruijing.

I want to try DPDK vhost with VPP v1704. Does dpdk vhost works in vpp1704? Any 
documentation on that would help.

If documentation is available for v1707 then I can switch to v1707 as well.

I am also looking for any vhost-user performance benchmark numbers on x86. Do 
we have benchmark numbers for both: VPP vhost-user and DPDK vhost?

Thanks,

Nitin

From: Steven Luong (sluong) mailto:slu...@cisco.com>>
Sent: Monday, September 11, 2017 7:46 PM
To: Guo, Ruijing; Saxena, Nitin; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

If you create the VIrtualEthernet interface via the CLI or binary API, it 
always uses VPP native. If you create the virtual interface via vdev in the 
dpdk clause in the startup file, it uses dpdk’s vhost-user.

The problem is in DPDK virtio-user that they don’t comply with virtio1.0 spec. 
I submitted a patch for them. I don’t think they took it yet.

Steven

From: mailto:vpp-dev-boun...@lists.fd.io>> on 
behalf of "Guo, Ruijing" mailto:ruijing@intel.com>>
Date: Sunday, September 10, 2017 at 5:36 PM
To: "Saxena, Nitin" mailto:nitin.sax...@cavium.com>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Just for your reference:

I am using vpp 17.07. The default one is vpp native. But it cannot work with 
virtio-user. So I change to vhost-user in dpdk.

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Saxena, Nitin
Sent: Monday, September 11, 2017 1:22 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Hi All

I went through following video regarding vhost-user.

https://www.youtube.com/watch?v=z-ZRof2hDP0

The question is in this video it has been told by default VPP implementation of 
vhost-user being used and not the dpdk one. Since this video is 1 yr old and I 
am using vpp version 1704. Can anyone please comment which vhost-user code is 
by default enabled in vpp1704 - is it dpdk one or VPP native? I can see in 
vpp-master/RELEASE.md that DPDK vhost was deprecated in vpp1609? Is it fixed 
now?

Thanks,

Nitin
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] [vhost-user][armv8][v1704]: VPP crashes while giving IP to VM interface

2017-09-15 Thread Saxena, Nitin

Hi All,


I am trying vhost-user configuration on Cavium's aarch64 SoC using VPP v1704. I 
mainly followed steps provided at following


https://wiki.fd.io/view/VPP/Use_VPP_to_connect_VMs_Using_Vhost-User_Interface


I am able to launch two VM's using qemu-system-aarch64. The host and guest 
kernel version is 4.12.9. I am also able to configure two virtual interface 
described in above documentation link. However as soon as I provide IP address 
to first VM interface using ifconfig or ip addr add command, the vpp process on 
host crashes. I was watching "vppctl show_interface" where I saw one packet 
received by vpp at Virtual1 interface and after then I think vpp process 
crashed so vppctl got hang.


I have attached gdb crash dump "gdb_crash_log.txt". I have also attached 
command I used to launch VM1 and VM2: vm1_launch.sh, vm2_launch.sh.


Any pointers will be really helpful.


Thanks,

Nitin





bridge_setup_vswitch.sh
Description: bridge_setup_vswitch.sh
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/home/nsaxena/vpp/v1704/build-root/install-vpp-native/vpp/bin/vpp...done.
(gdb) r
Starting program: 
/home/nsaxena/vpp/v1704/build-root/install-vpp-native/vpp/bin/vpp -c 
/etc/vpp/startup.conf
warning: Unable to determine the number of hardware watchpoints available.
warning: Unable to determine the number of hardware breakpoints available.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
vlib_plugin_early_init:360: plugin path 
/home/nsaxena/vpp/v1704/build-root/install-vpp-native/vpp/lib/vpp_plugins
load_one_plugin:188: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:188: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:188: Loaded plugin: flowperpkt_plugin.so (Flow per Packet)
load_one_plugin:188: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:188: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:83: Not a plugin: ixge_plugin.so
load_one_plugin:188: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:188: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid Deployment 
on IPv4 Infrastructure (RFC5969))
load_one_plugin:188: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimetal))
load_one_plugin:188: Loaded plugin: snat_plugin.so (Network Address Translation)
0: dpdk_bind_devices_to_uio:1158: Unsupported PCI device 0x14e4:0x16a1 found at 
PCI address :0b:00.0
0: vlib_pci_bind_to_uio: Skipping PCI device :13:00.1 as host interface 
enp19s0f1 is up
0: dpdk_bind_devices_to_uio:1158: Unsupported PCI device 0x14e4:0x16a1 found at 
PCI address :0b:00.1
0: vlib_pci_bind_to_uio: Skipping PCI device :13:00.0 as host interface 
enp19s0f0 is up
EAL: Detected 224 lcore(s)
EAL: Probing VFIO support...
[New Thread 0x32fba1f0 (LWP 23821)]
EAL: PCI device :13:00.0 on NUMA socket 0
EAL:   Device is blacklisted, not initializing
EAL: PCI device :13:00.1 on NUMA socket 0
EAL:   Device is blacklisted, not initializing
DPDK physical memory layout:
Segment 0: phys:0x9f1780, len:268435456, virt:0x0c60, socket_id:0, 
hugepage_sz:2097152, nchannel:0, nrank:0
Segment 1: phys:0xbf1d80, len:268435456, virt:0xfffed240, socket_id:1, 
hugepage_sz:2097152, nchannel:0, nrank:0
[New Thread 0x327ba1f0 (LWP 23822)]
/home/nsaxena/vpp/v1704/build-root/install-vpp-native/vpp/bin/vpp[23818]: 
dpdk_ipsec_process:241: DPDK Cryptodev support is disabled, default to OpenSSL 
IPsec
/home/nsaxena/vpp/v1704/build-root/install-vpp-native/vpp/bin/vpp[23818]: 
dpdk_lib_init:536: DPDK drivers found no ports...
Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault.
vlib_buffer_free_inline (follow_buffer_next=1, n_buffers=65535, 
buffers=0x778e8000,
vm=0xb7f99ed0 ) at 
/home/nsaxena/vpp/v1704/build-data/../src/plugins/dpdk/buffer.c:360
360   if (PREDICT_FALSE (fl->buffers_added_to_freelist_function != 0))
(gdb) bt
#0  vlib_buffer_free_inline (follow_buffer_next=1, n_buffers=65535, 
buffers=0x778e8000,
vm=0xb7f99ed0 ) at 
/home/nsaxena/vpp/v1704/build-data/../src/plugins/dpdk/buffer.c:360
#1  dpdk_buffer_free (vm=0xb7f99ed0 , 
buffers=0x778e8000, n_buffers=)
at /

[vpp-dev] plugin compile error

2017-09-15 Thread ????????

Hi, everyone:
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
make  all-am
make[1]: Entering directory `/home/plugins/myplugin'
   API
 at line 1ken 
(null):1 syntax error
Removing myplugin.api.json
make[1]: *** [myplugin.api.json] Error 1
make[1]: Leaving directory `/home/plugins/myplugin'
make: *** [all] Error 2


I don''t know why? Can anyone help me? THank you!___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] plugin compile error

2017-09-15 Thread Luke, Chris

It’s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file from API_FILES in the .am of the plugin.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of 
Sent: Friday, September 15, 2017 10:46
To: vpp-dev 
Subject: [vpp-dev] plugin compile error

Hi, everyone:
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
make  all-am
make[1]: Entering directory `/home/plugins/myplugin'
   API
 at line 1ken
(null):1 syntax error
Removing myplugin.api.json
make[1]: *** [myplugin.api.json] Error 1
make[1]: Leaving directory `/home/plugins/myplugin'
make: *** [all] Error 2

I don''t know why? Can anyone help me? THank you!

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Jenkins ubuntu 1604 failures

2017-09-15 Thread Vanessa Valderrama

VPP Jenkins minions have been switched to 4 core / 16GB instances.  I'll
be monitoring builds throughout the day.  Please contact me via IRC
fdio-infra (valderrv) if you experience any issues.

Thank you,
Vanessa

On 09/14/2017 05:59 PM, Vanessa Valderrama wrote:
>
> Florin,
>
> It doesn't appear the  failures are related to the new instances.  We
> will be switching to a new performance (4c/8GB) instance when it's
> available. I've submitted a request to the vendor and will follow up
> tomorrow morning.  Adding the additional CPU resources may
> improve/resolve the failure in build 7108.  Please let me know if
> there are additional failures you are concerned about that I haven't
> addressed.  Also please feel free to ping me via IRC fdio-infra
> (valderrv) if you'd like to work together to debug these issues quickly.
>
> *https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7108/console
> 17:34:21* ACL IPv4 routed -> bridged, L2 ACL
> permit+reflect17:44:47,177 Timeout while waiting for child test runner
> process (last test running was `MACIP 2 ACLs each with 100+ entries'
> in `/tmp/vpp-unittest-TestMACIP-py7viS')!
>
> *
> *This failure is not a timeout and appears to be related to code*
>
> https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7109/console* 
>   
>
> *16:48:11* * Test framework PEP8 compliance check FAILED
> *16:48:11*
> ***
> *16:48:11* Makefile:172: recipe for target 'checkstyle' failed
> *16:48:11* make[1]: *** [checkstyle]
> Error 1 *16:48:11* make[1]: Leaving directory
> '/w/workspace/vpp-verify-master-ubuntu1604/test' *16:48:11*
> Makefile:376: recipe for target 'test-checkstyle' failed *16:48:11*
> make: *** [test-checkstyle] Error 2 *16:48:11* Build step
> 'Execute shell' marked build as failure
>
>
> The cause of these two failures appear to be related to package(s) not
> installing?
> *   
> https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7111/console
>
> https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7112/console
> **19:05:38* cc1: all warnings being treated as errors
> *19:05:38* Makefile:6164: recipe for target 'vppinfra/linux/mem.lo'
> failed *19:05:38* make[3]: *** [vppinfra/linux/mem.lo] Error 1
> *19:05:38* make[3]: *** Waiting for unfinished jobs *   
> 19:05:40* make[3]: Leaving directory
> '/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp'*19:05:40*
> Makefile:698: recipe for target 'vpp-build' failed *19:05:40* make[2]:
> *** [vpp-build] Error 2 *19:05:40* make[2]:
> Leaving directory
> '/w/workspace/vpp-verify-master-ubuntu1604/build-root' *19:05:40*
> Makefile:934: recipe for target 'install-packages' failed *19:05:40*
> make[1]: *** [install-packages] Error 1 *19:05:40* make[1]: Leaving
> directory '/w/workspace
> /vpp-verify-master-ubuntu1604/build-root' *19:05:40* Makefile:487:
> recipe for target 'verify' failed *19:05:40* make: *** [verify] Error
> 2 *19:05:40* Build step 'Execute shell' marked build as failure
>
> Thank you,
> Vanessa
>
> On 09/14/2017 02:27 PM, Florin Coras wrote:
>> Hi Vanessa, 
>>
>> We’re seeing lots of vpp-verify-master-ubuntu1604 failures that seem to be 
>> timeouts related. Could they be related to the recent switch to the new 
>> instances?
>>
>> Thanks, 
>> Florin
>>
>



signature.asc
Description: OpenPGP digital signature
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] [FD.io Helpdesk #45822] [linuxfoundation.org #45822] Re: Jenkins ubuntu 1604 failures

2017-09-15 Thread Vanessa Valderrama via RT

VPP Jenkins minions have been switched to 4 core / 16GB instances.  I'll
be monitoring builds throughout the day.  Please contact me via IRC
fdio-infra (valderrv) if you experience any issues.

Thank you,
Vanessa

On 09/14/2017 05:59 PM, Vanessa Valderrama wrote:
>
> Florin,
>
> It doesn't appear the  failures are related to the new instances.  We
> will be switching to a new performance (4c/8GB) instance when it's
> available. I've submitted a request to the vendor and will follow up
> tomorrow morning.  Adding the additional CPU resources may
> improve/resolve the failure in build 7108.  Please let me know if
> there are additional failures you are concerned about that I haven't
> addressed.  Also please feel free to ping me via IRC fdio-infra
> (valderrv) if you'd like to work together to debug these issues quickly.
>
> *https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7108/console
> 17:34:21* ACL IPv4 routed -> bridged, L2 ACL
> permit+reflect17:44:47,177 Timeout while waiting for child test runner
> process (last test running was `MACIP 2 ACLs each with 100+ entries'
> in `/tmp/vpp-unittest-TestMACIP-py7viS')!
>
> *
> *This failure is not a timeout and appears to be related to code*
>
> https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7109/console* 
>   
>
> *16:48:11* * Test framework PEP8 compliance check FAILED
> *16:48:11*
> ***
> *16:48:11* Makefile:172: recipe for target 'checkstyle' failed
> *16:48:11* make[1]: *** [checkstyle]
> Error 1 *16:48:11* make[1]: Leaving directory
> '/w/workspace/vpp-verify-master-ubuntu1604/test' *16:48:11*
> Makefile:376: recipe for target 'test-checkstyle' failed *16:48:11*
> make: *** [test-checkstyle] Error 2 *16:48:11* Build step
> 'Execute shell' marked build as failure
>
>
> The cause of these two failures appear to be related to package(s) not
> installing?
> *   
> https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7111/console
>
> https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7112/console
> **19:05:38* cc1: all warnings being treated as errors
> *19:05:38* Makefile:6164: recipe for target 'vppinfra/linux/mem.lo'
> failed *19:05:38* make[3]: *** [vppinfra/linux/mem.lo] Error 1
> *19:05:38* make[3]: *** Waiting for unfinished jobs *   
> 19:05:40* make[3]: Leaving directory
> '/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp'*19:05:40*
> Makefile:698: recipe for target 'vpp-build' failed *19:05:40* make[2]:
> *** [vpp-build] Error 2 *19:05:40* make[2]:
> Leaving directory
> '/w/workspace/vpp-verify-master-ubuntu1604/build-root' *19:05:40*
> Makefile:934: recipe for target 'install-packages' failed *19:05:40*
> make[1]: *** [install-packages] Error 1 *19:05:40* make[1]: Leaving
> directory '/w/workspace
> /vpp-verify-master-ubuntu1604/build-root' *19:05:40* Makefile:487:
> recipe for target 'verify' failed *19:05:40* make: *** [verify] Error
> 2 *19:05:40* Build step 'Execute shell' marked build as failure
>
> Thank you,
> Vanessa
>
> On 09/14/2017 02:27 PM, Florin Coras wrote:
>> Hi Vanessa, 
>>
>> We’re seeing lots of vpp-verify-master-ubuntu1604 failures that seem to be 
>> timeouts related. Could they be related to the recent switch to the new 
>> instances?
>>
>> Thanks, 
>> Florin
>>
>


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] ??????RE: plugin compile error

2017-09-15 Thread ????????

Hi, Luke,
   Thank your reply. I have written some apis. The .json file and 
myplugin.api.h file have made  correctly.. Any other problems? 




--  --
??: "Luke, Chris";;
: 2017??9??15??(??) 11:11
??: ""<15803846...@qq.com>; "vpp-dev"; 

: RE: [vpp-dev] plugin compile error



  
It??s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file from API_FILES in the .am of the plugin.
 
 
 
Chris.
 
 

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of 
 Sent: Friday, September 15, 2017 10:46
 To: vpp-dev 
 Subject: [vpp-dev] plugin compile error
 
 
 
 
  
Hi, everyone:
 
  
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
 
   
make  all-am
 
  
make[1]: Entering directory `/home/plugins/myplugin'
 
  
   API
 
  
 at line 1ken 
 
  
(null):1 syntax error
 
  
Removing myplugin.api.json
 
  
make[1]: *** [myplugin.api.json] Error 1
 
  
make[1]: Leaving directory `/home/plugins/myplugin'
 
  
make: *** [all] Error 2
 
  
 
 
  
I don''t know why? Can anyone help me? THank you!___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 回复：RE: plugin compile error

2017-09-15 Thread Luke, Chris

Can you show your .api and the generated .json?

Chris.

From: 重新开始 [mailto:15803846...@qq.com]
Sent: Friday, September 15, 2017 11:51
To: Luke, Chris ; vpp-dev 
Subject: 回复：RE: [vpp-dev] plugin compile error

Hi, Luke,
   Thank your reply. I have written some apis. The .json file and 
myplugin.api.h file have made  correctly.. Any other problems?

-- 原始邮件 --
发件人: "Luke, Chris";mailto:chris_l...@comcast.com>>;
发送时间: 2017年9月15日(星期五) 晚上11:11
收件人: "重新开始"<15803846...@qq.com>; 
"vpp-dev"mailto:vpp-dev@lists.fd.io>>;
主题: RE: [vpp-dev] plugin compile error

It’s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file from API_FILES in the .am of the plugin.

Chris.

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of 
Sent: Friday, September 15, 2017 10:46
To: vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] plugin compile error

Hi, everyone:
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
make  all-am
make[1]: Entering directory `/home/plugins/myplugin'
   API
 at line 1ken
(null):1 syntax error
Removing myplugin.api.json
make[1]: *** [myplugin.api.json] Error 1
make[1]: Leaving directory `/home/plugins/myplugin'
make: *** [all] Error 2

I don''t know why? Can anyone help me? THank you!

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] ??????RE: ??????RE: plugin compile error

2017-09-15 Thread ????????

--  --
??: "Luke, Chris";;
: 2017??9??16??(??) 0:08
??: ""<15803846...@qq.com>; "vpp-dev"; 

: RE: ??RE: [vpp-dev] plugin compile error



  
Can you show your .api and the generated .json?
 
 
 
Chris.
 
 

From:  [mailto:15803846...@qq.com] 
 Sent: Friday, September 15, 2017 11:51
 To: Luke, Chris ; vpp-dev 
 Subject: ??RE: [vpp-dev] plugin compile error
 
 
 
 
  
Hi, Luke,
 
  
   Thank your reply. I have written some apis. The .json file and 
myplugin.api.h file have made  correctly.. Any other problems? 
 
   
 
 
  
 
 
  
--  --
 
   
??: "Luke, Chris";;
 
  
: 2017??9??15??(??) 11:11
 
  
??: ""<15803846...@qq.com>;  "vpp-dev"; 
 
  
: RE: [vpp-dev] plugin compile error
 
 
  
 
 
  
It??s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file  from API_FILES in the .am of the plugin.
 
 
 
Chris.
 
 

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of 
 Sent: Friday, September 15, 2017 10:46
 To: vpp-dev 
 Subject: [vpp-dev] plugin compile error
 
 
 
 
  
Hi, everyone:
 
  
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
 
   
make  all-am
 
  
make[1]: Entering directory `/home/plugins/myplugin'
 
  
   API
 
  
 at line 1ken 
 
  
(null):1 syntax error
 
  
Removing myplugin.api.json
 
  
make[1]: *** [myplugin.api.json] Error 1
 
  
make[1]: Leaving directory `/home/plugins/myplugin'
 
  
make: *** [all] Error 2
 
  
 
 
  
I don''t know why? Can anyone help me? THank you!

vpncrack.api
Description: Binary data


vpncrack.api.h
Description: Binary data


vpncrack.api.json
Description: Binary data
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] VPP API Message Multi-Registration Question

2017-09-15 Thread Jon Loeliger

Folks,

We have a need to re-register API message handlers.
(Think re-fork/exec scenarios for daemons.)

Today, we register handlers via a call to this function:

vl_msg_api_set_handlers (int id, char *name, void *handler, void *cleanup,
 void *endian, void *print, int size, int traced)

When we do that today, we see this warning on the second call.

vl_msg_api_config (vl_msg_api_msg_config_t * c)
{

  [...]

  if (am->msg_names[c->id])
clib_warning ("BUG: multiple registrations of 'vl_api_%s_t_handler'",
  c->name);

  am->msg_names[c->id] = c->name;
  am->msg_handlers[c->id] = c->handler;
  am->msg_cleanup_handlers[c->id] = c->cleanup;
  am->msg_endian_handlers[c->id] = c->endian;
  am->msg_print_handlers[c->id] = c->print;
  am->message_bounce[c->id] = c->message_bounce;
  am->is_mp_safe[c->id] = c->is_mp_safe;

Sure, the handler is re-registered, but it is really annoying,
and it is misleading in our case.  So we are looking for a
way to squelch it.

Is there a way to *un*-bind a handler during a "graceful shutdown"
procedure so that we can remove any binding here, and thus
later when we re-bind it is all happy again?

Or, can we call a (new?) API function that says "Yeah, we know,
but squash that message for me." just prior to registering the
handlers.

Or, is there a graceful shutdown of the API handling that
I have just missed or overlooked somewhere?

Thanks,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 回复：RE: 回复：RE: plugin compile error

2017-09-15 Thread Luke, Chris

There’s nothing obvious in these files; I guess I need to see your .am file. It 
would be easier if you could just share your plugin whole, perhaps on github.

Chris.

From: 重新开始 [mailto:15803846...@qq.com]
Sent: Friday, September 15, 2017 12:15
To: Luke, Chris ; vpp-dev 
Subject: 回复：RE: 回复：RE: [vpp-dev] plugin compile error

-- 原始邮件 --
发件人: "Luke, Chris";mailto:chris_l...@comcast.com>>;
发送时间: 2017年9月16日(星期六) 凌晨0:08
收件人: "重新开始"<15803846...@qq.com>; 
"vpp-dev"mailto:vpp-dev@lists.fd.io>>;
主题: RE: 回复：RE: [vpp-dev] plugin compile error

Can you show your .api and the generated .json?

Chris.

From: 重新开始 [mailto:15803846...@qq.com]
Sent: Friday, September 15, 2017 11:51
To: Luke, Chris 
mailto:chris_l...@cable.comcast.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: 回复：RE: [vpp-dev] plugin compile error

Hi, Luke,
   Thank your reply. I have written some apis. The .json file and 
myplugin.api.h file have made  correctly.. Any other problems?

-- 原始邮件 --
发件人: "Luke, Chris";mailto:chris_l...@comcast.com>>;
发送时间: 2017年9月15日(星期五) 晚上11:11
收件人: "重新开始"<15803846...@qq.com>; 
"vpp-dev"mailto:vpp-dev@lists.fd.io>>;
主题: RE: [vpp-dev] plugin compile error

It’s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file from API_FILES in the .am of the plugin.

Chris.

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of 
Sent: Friday, September 15, 2017 10:46
To: vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] plugin compile error

Hi, everyone:
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
make  all-am
make[1]: Entering directory `/home/plugins/myplugin'
   API
 at line 1ken
(null):1 syntax error
Removing myplugin.api.json
make[1]: *** [myplugin.api.json] Error 1
make[1]: Leaving directory `/home/plugins/myplugin'
make: *** [all] Error 2

I don''t know why? Can anyone help me? THank you!

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP API Message Multi-Registration Question

2017-09-15 Thread Dave Barach (dbarach)

How about: only complain if the new registration is actually different from the 
old one?

Thanks... Dave

-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Jon Loeliger
Sent: Friday, September 15, 2017 3:35 PM
To: vpp-dev 
Subject: [vpp-dev] VPP API Message Multi-Registration Question

Folks,

We have a need to re-register API message handlers.
(Think re-fork/exec scenarios for daemons.)

Today, we register handlers via a call to this function:

vl_msg_api_set_handlers (int id, char *name, void *handler, void *cleanup,
 void *endian, void *print, int size, int traced)

When we do that today, we see this warning on the second call.

vl_msg_api_config (vl_msg_api_msg_config_t * c)
{

  [...]

  if (am->msg_names[c->id])
clib_warning ("BUG: multiple registrations of 'vl_api_%s_t_handler'",
  c->name);

  am->msg_names[c->id] = c->name;
  am->msg_handlers[c->id] = c->handler;
  am->msg_cleanup_handlers[c->id] = c->cleanup;
  am->msg_endian_handlers[c->id] = c->endian;
  am->msg_print_handlers[c->id] = c->print;
  am->message_bounce[c->id] = c->message_bounce;
  am->is_mp_safe[c->id] = c->is_mp_safe;

Sure, the handler is re-registered, but it is really annoying,
and it is misleading in our case.  So we are looking for a
way to squelch it.

Is there a way to *un*-bind a handler during a "graceful shutdown"
procedure so that we can remove any binding here, and thus
later when we re-bind it is all happy again?

Or, can we call a (new?) API function that says "Yeah, we know,
but squash that message for me." just prior to registering the
handlers.

Or, is there a graceful shutdown of the API handling that
I have just missed or overlooked somewhere?

Thanks,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] usability: API message table comparison

2017-09-15 Thread Dave Barach (dbarach)

Here is a comparison report between a master/latest image, and a 17.07.1 image. 
"only in image" means that the message is defined in master/latest, but not in 
17.07.1. 

 Message Name Result
bridge_domain_add_deldefinition changed
bridge_domain_detailsdefinition changed
connect_session  definition changed
connect_sock definition changed
connect_sock_reply   definition changed
connect_uri_replydefinition changed
create_vhost_user_if definition changed
dhcp_client_config   definition changed
ip4_arp_eventdefinition changed
ip6_fib_details  definition changed
ip6_nd_event definition changed
ip_add_del_route definition changed
ip_fib_details   definition changed
ip_table_add_del definition changed
l2_macs_eventonly in image
macip_acl_add_replacedefinition changed
macip_acl_interface_list_details only in image
macip_acl_interface_list_dumponly in image
modify_vhost_user_if definition changed
mpls_fib_details definition changed
mpls_route_add_del   definition changed
mpls_table_add_del   definition changed
mpls_tunnel_add_del  definition changed
nat44_add_del_address_range  definition changed
nat44_add_del_interface_addr definition changed
nat44_add_del_lb_static_mapping  definition changed
nat44_add_del_static_mapping definition changed
nat44_address_detailsonly in image
nat44_address_dump   only in image
nat44_interface_add_del_feature  definition changed
nat44_interface_add_del_output_feature   definition changed
nat44_interface_addr_details only in image
nat44_interface_addr_dumponly in image
nat44_interface_details  only in image
nat44_interface_dump only in image
nat44_interface_output_feature_details   only in image
nat44_interface_output_feature_dump  only in image
nat44_lb_static_mapping_details  only in image
nat44_lb_static_mapping_dump only in image
nat44_static_mapping_details only in image
nat44_static_mapping_dumponly in image
nat44_user_details   only in image
nat44_user_dump  only in image
nat44_user_session_details   only in image
nat44_user_session_dump  only in image
nat_control_ping definition changed
nat_det_add_del_map  definition changed
nat_det_close_session_in definition changed
nat_det_close_session_outdefinition changed
nat_det_forward  definition changed
nat_det_get_timeouts definition changed
nat_det_map_details  only in image
nat_det_map_dump only in image
nat_det_reverse  definition changed
nat_det_session_details  only in image
nat_det_session_dump only in image
nat_det_set_timeouts definition changed
nat_ipfix_enable_disable definition changed
nat_set_workers  definition changed
nat_show_config  definition changed
nat_worker_details   only in imag

[vpp-dev] VPP API for setting routes and MPLS

2017-09-15 Thread Michael Borokhovich

Hi,

Are there APIs available for setting routes and MPLS labels?
Would be great to have REST APIs, but it looks like Honecomb does not
support these operations.

Are there Jvpp APIs for these operations so that we would be able to create
Honecomb plugins for them?

The operations I'm talking about are e.g.,

vppctl mpls local-label add eos 333 ip4-lookup-in-table 2

vppctl ip route add 10.0.0.0/24 table 1 via 10.0.4.12 GigabitEthernet0/6/0
out-label 222

Thanks,
Michael.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] coross compile

2017-09-15 Thread yug...@telincn.com

Hi all.
Is there a way to cross compile vpp?
How to compile vpp for ubuntu  on centos?

Regards,
Ewan 



yug...@telincn.com
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

Re: [vpp-dev] vhost-user stable implementation?: VPP native or DPDK

[vpp-dev] [vhost-user][armv8][v1704]: VPP crashes while giving IP to VM interface

[vpp-dev] plugin compile error

Re: [vpp-dev] plugin compile error

Re: [vpp-dev] Jenkins ubuntu 1604 failures

[vpp-dev] [FD.io Helpdesk #45822] [linuxfoundation.org #45822] Re: Jenkins ubuntu 1604 failures

[vpp-dev] ??????RE: plugin compile error

Re: [vpp-dev] 回复：RE: plugin compile error

[vpp-dev] ??????RE: ??????RE: plugin compile error

[vpp-dev] VPP API Message Multi-Registration Question

Re: [vpp-dev] 回复：RE: 回复：RE: plugin compile error

Re: [vpp-dev] VPP API Message Multi-Registration Question

Re: [vpp-dev] usability: API message table comparison

[vpp-dev] VPP API for setting routes and MPLS

[vpp-dev] coross compile

19 matches

Site Navigation

Mail list logo

Footer information