[vpp-dev] WAN Failover

2019-08-09 Thread carlito nueno 
Hi all,

I am using VPP (19.04.1) as a gateway and I have two WAN connections.
I want to setup failover with the two WAN interfaces.

Example:
1. Connection on WAN-0 is lost (due to ISP being down)
2. WAN-1 becomes the new primary connection and traffic flows via WAN-1
3. WAN-0 is back up
4. WAN-0 becomes the primary connection and all traffic from WAN-1 now
flows via WAN-0

I setup bond interface and NAT44. It sort of works. When WAN-0 is
unplugged, WAN-1 become primary but when WAN-0 is plugged back in,
WAN-1 remains the primary.

But I want the primary to switch when traffic fails to traverse not
when the cable is physically unplugged.

startup.conf
---
vdev eth_bond0,mode=0,slave=:05:00.0,slave=:04:00.0


vpp.conf

set int state BondEthernet0 up
set int ip address BondEthernet0 10.100.1.2/24
set int ip address BondEthernet0 10.200.1.2/24
ip route add 0.0.0.0/0 via 10.100.1.1 BondEthernet0
ip route add 0.0.0.0/0 via 10.200.1.1 BondEthernet0

set int state lan0 up
set int state lan1 up

nat44 add interface address BondEthernet0
set interface nat44 in lan0 in lan1 out BondEthernet0

Let me know if you need more information.

Really appreciate the help!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13706): https://lists.fd.io/g/vpp-dev/message/13706
Mute This Topic: https://lists.fd.io/mt/32817575/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] query regarding memif

2019-08-09 Thread Dave Barach via Lists.Fd.Io 
Please try w/ master/latest or stable/1908.

From: vpp-dev@lists.fd.io  On Behalf Of via Lists.Fd.Io
Sent: Wednesday, August 7, 2019 9:22 AM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] query regarding memif

Hi,

I am using vpp version 18.01.01 and i am getting a crash in memif plugin. The 
scenario is that, the worker thread is processing traffic from memif and the 
main thread deleted the memif. Is there any corner scenario where in the worker 
can crash because of the memif getting deleted.
The worker thread is crashing when it is trying to access the memif queue ring.

Please let me know if this type of scenario can crash the worker thread.

back trace:

 0x00022c21: signal_handler at 
/epc-scaled/epc3/services/epcu/common/prdp/src/datapath/vpp-plugins/build/../../../common/inc/bt.h:349

  0x7feedd30df20: ?? ??:0

  0x0001c401: memif_device_input_inline at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/plugins/memif/node.c:275

   (inlined by) memif_input_fn_avx2 at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/plugins/memif/node.c:481

  0x00035e68: dispatch_node at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:988

   (inlined by) vlib_main_or_worker_loop at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:1506

   (inlined by) vlib_main_loop at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:1628

   (inlined by) vlib_main at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:1783

  0x0006c396: unformat_free at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vppinfra/format.h:163

   (inlined by) thread0 at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/unix/main.c:568





Regards,

Manjunath

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13705): https://lists.fd.io/g/vpp-dev/message/13705
Mute This Topic: https://lists.fd.io/mt/32812057/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 20.01 arch linux build problem

2019-08-09 Thread Алексей 
GCC 9.2
Platform: archlinux 

VPP version : 20.01-rc0~1-gf16826e7b
VPP library version : 20.01
GIT toplevel dir: /home/user/Sources/vpp
Build type  : 
C flags : -Wno-address-of-packed-member -march=corei7 
-mtune=corei7-avx -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-protector 
-fPIC -Wall -Werror -fno-common
Linker flags: -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-protector 
-fPIC -Wall -Werror -fno-common
Host processor  : x86_64
Target processor: x86_64
Prefix path : 
/opt/vpp/external/x86_64;/home/user/Sources/vpp/build-root/install-vpp_debug-native/external
Install prefix  : 
/home/user/Sources/vpp/build-root/install-vpp_debug-native/vpp
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/user/Sources/vpp/build-root/build-vpp_debug-native/vpp
 Building vpp in 
/home/user/Sources/vpp/build-root/build-vpp_debug-native/vpp 
[1/734] Building C object 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o
FAILED: plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o 
/usr/bin/cc -DHAVE_GETCPU -DHAVE_MEMFD_CREATE -I/home/user/Sources/vpp/src -I. 
-Iinclude -I/home/user/Sources/vpp/src/plugins -Iplugins 
-Wno-address-of-packed-member -march=corei7 -mtune=corei7-avx -O0 -DCLIB_DEBUG 
-g -DFORTIFY_SOURCE=2 -fstack-protector -fPIC -Wall -Werror -fno-common -fPIC   
-march=silvermont -Wall -fno-common -MD -MT 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o -MF 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o.d -o 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o   -c 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
 from /home/user/Sources/vpp/src/vppinfra/string.h:48,
 from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
 from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
 from /home/user/Sources/vpp/src/vppinfra/format.h:44,
 from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
 from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
 from /home/user/Sources/vpp/src/vlib/vlib.h:44,
 from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h: В функции 
«aes_key_enc_to_dec»:
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка: 
inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не 
выполнена: target specific option mismatch
   77 | _mm_aesimc_si128 (__m128i __X)
  | ^~~~
In file included from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:212:14: замечание: 
которая вызвана здесь
  212 |   k[i] = _mm_aesimc_si128 (r);
  |  ^~~~
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
 from /home/user/Sources/vpp/src/vppinfra/string.h:48,
 from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
 from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
 from /home/user/Sources/vpp/src/vppinfra/format.h:44,
 from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
 from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
 from /home/user/Sources/vpp/src/vlib/vlib.h:44,
 from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка: 
inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не 
выполнена: target specific option mismatch
   77 | _mm_aesimc_si128 (__m128i __X)
  | ^~~~
In file included from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:211:23: замечание: 
которая вызвана здесь
  211 |   k[rounds - i] = _mm_aesimc_si128 (k[i]);
  |   ^~~
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,

[vpp-dev] query regarding memif

2019-08-09 Thread via Lists.Fd.Io 
Hi,I am using vpp version 18.01.01 and i am getting a crash in memif plugin. 
The scenario is that, the worker thread is processing traffic from memif and 
the main thread deleted the memif. Is there any corner scenario where in the 
worker can crash because of the memif getting deleted.The worker thread is 
crashing when it is trying to access the memif queue ring.Please let me know if 
this type of scenario can crash the worker thread.back trace: 
0x00022c21: signal_handler at 
/epc-scaled/epc3/services/epcu/common/prdp/src/datapath/vpp-plugins/build/../../../common/inc/bt.h:349
  0x7feedd30df20: ?? ??:0
  0x0001c401: memif_device_input_inline at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/plugins/memif/node.c:275
   (inlined by) memif_input_fn_avx2 at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/plugins/memif/node.c:481
  0x00035e68: dispatch_node at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:988
   (inlined by) vlib_main_or_worker_loop at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:1506
   (inlined by) vlib_main_loop at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:1628
   (inlined by) vlib_main at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/main.c:1783
  0x0006c396: unformat_free at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vppinfra/format.h:163
   (inlined by) thread0 at 
/root/bkn/xfe/datapath/vpp/src/build-data/../src/vlib/unix/main.c:568


Regards,
Manjunath
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13701): https://lists.fd.io/g/vpp-dev/message/13701
Mute This Topic: https://lists.fd.io/mt/32812057/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Envoy transport socket support for vpp.

2019-08-09 Thread via Lists.Fd.Io 
Hi Rupesh,

I have been working on this and it is getting close. Ping and I are currently 
debugging a few issues and it basically will be working in a week or two. The 
code is not upstreamed yet- I'll be bringing up the next steps required at the 
next Envoy community meeting.

Note that the integration of VCL and Envoy goes far beyond a new type of 
transport socket, since VCL has its own events, workers and listeners. You can 
contact me directly if you have more questions. Thanks,

-stephen


On 8/6/19, 11:38 AM, "Florin Coras"  wrote:

Hi Rupesh, 

CC’ing Stephen and Ping who are working on this. 

Florin

> On Aug 5, 2019, at 4:36 AM, Rupesh Raghuvaran 
 wrote:
> 
> Hi,
> 
> I would like to know the current state of the support for envoy over vpp 
host stack. Is there any open source transport socket support for vpp available 
for envoy.
> 
> Thanks
> Rupesh  -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#13661): https://lists.fd.io/g/vpp-dev/message/13661
> Mute This Topic: https://lists.fd.io/mt/32724370/675152
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [fcoras.li...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13700): https://lists.fd.io/g/vpp-dev/message/13700
Mute This Topic: https://lists.fd.io/mt/32724370/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 20.01 buid failed.

2019-08-09 Thread Алексей Болдырев 
GCC 9.2
Platform: archlinux 

VPP version : 20.01-rc0~1-gf16826e7b
VPP library version : 20.01
GIT toplevel dir: /home/user/Sources/vpp
Build type  : 
C flags : -Wno-address-of-packed-member -march=corei7 
-mtune=corei7-avx -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-protector 
-fPIC -Wall -Werror -fno-common
Linker flags: -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-protector 
-fPIC -Wall -Werror -fno-common
Host processor  : x86_64
Target processor: x86_64
Prefix path : 
/opt/vpp/external/x86_64;/home/user/Sources/vpp/build-root/install-vpp_debug-native/external
Install prefix  : 
/home/user/Sources/vpp/build-root/install-vpp_debug-native/vpp
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/user/Sources/vpp/build-root/build-vpp_debug-native/vpp
 Building vpp in 
/home/user/Sources/vpp/build-root/build-vpp_debug-native/vpp 
[1/734] Building C object 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o
FAILED: plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o 
/usr/bin/cc -DHAVE_GETCPU -DHAVE_MEMFD_CREATE -I/home/user/Sources/vpp/src -I. 
-Iinclude -I/home/user/Sources/vpp/src/plugins -Iplugins 
-Wno-address-of-packed-member -march=corei7 -mtune=corei7-avx -O0 -DCLIB_DEBUG 
-g -DFORTIFY_SOURCE=2 -fstack-protector -fPIC -Wall -Werror -fno-common -fPIC   
-march=silvermont -Wall -fno-common -MD -MT 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o -MF 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o.d -o 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o   -c 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
 from /home/user/Sources/vpp/src/vppinfra/string.h:48,
 from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
 from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
 from /home/user/Sources/vpp/src/vppinfra/format.h:44,
 from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
 from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
 from /home/user/Sources/vpp/src/vlib/vlib.h:44,
 from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h: В функции 
«aes_key_enc_to_dec»:
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка: 
inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не 
выполнена: target specific option mismatch
   77 | _mm_aesimc_si128 (__m128i __X)
  | ^~~~
In file included from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:212:14: замечание: 
которая вызвана здесь
  212 |   k[i] = _mm_aesimc_si128 (r);
  |  ^~~~
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
 from /home/user/Sources/vpp/src/vppinfra/string.h:48,
 from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
 from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
 from /home/user/Sources/vpp/src/vppinfra/format.h:44,
 from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
 from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
 from /home/user/Sources/vpp/src/vlib/vlib.h:44,
 from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка: 
inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не 
выполнена: target specific option mismatch
   77 | _mm_aesimc_si128 (__m128i __X)
  | ^~~~
In file included from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:211:23: замечание: 
которая вызвана здесь
  211 |   k[rounds - i] = _mm_aesimc_si128 (k[i]);
  |   ^~~
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,

[vpp-dev] Arch Linux build problem

2019-08-09 Thread Алексей Болдырев 
Platform: arch linux
Gcc: gcc (GCC) 9.1.0
Log:
== Build lib/librte_meter 
== Build lib/librte_mempool
== Build lib/librte_efd
== Build lib/librte_member
== Build lib/librte_mbuf
== Build lib/librte_bbdev
== Build lib/librte_net
== Build lib/librte_cryptodev
== Build lib/librte_compressdev
== Build lib/librte_sched
== Build lib/librte_reorder
== Build lib/librte_ethdev
== Build lib/librte_security
== Build lib/librte_eventdev
== Build lib/librte_rawdev
== Build lib/librte_vhost
 CC iotlb.o
 CC socket.o
In file included from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:19,
 
from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/socket.c:22:
 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/x86_64-native-linuxapp-gcc/include/rte_ether.h:
 In functi
on ‘is_broadcast_ether_addr’: 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/x86_64-native-linuxapp-gcc/include/rte_ether.h:149:2:
 war
ning: converting a packed ‘const struct ether_addr’ pointer (alignment 1) to a 
‘unaligned_uint16_t’ {aka ‘const short unsigned int’} poi
nter (alignment 2) may result in an unaligned pointer value 
[-Waddress-of-packed-member] 
 149 |  const unaligned_uint16_t *ea_words = (const unaligned_uint16_t *)ea; 
 |  ^ 
In file included from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:19,
 
from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/iotlb.h:37,
 
from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/iotlb.c:39:
 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/x86_64-native-linuxapp-gcc/include/rte_ether.h:
 In functi
on ‘is_broadcast_ether_addr’: 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/x86_64-native-linuxapp-gcc/include/rte_ether.h:149:2:
 war
ning: converting a packed ‘const struct ether_addr’ pointer (alignment 1) to a 
‘unaligned_uint16_t’ {aka ‘const short unsigned int’} poi
nter (alignment 2) may result in an unaligned pointer value 
[-Waddress-of-packed-member] 
 149 |  const unaligned_uint16_t *ea_words = (const unaligned_uint16_t *)ea; 
 |  ^ 
In file included from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/iotlb.h:37,
 
from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/iotlb.c:39:
 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:
 In function ‘desc_is_avail’: 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:387:42:
 error: ‘VRING_DESC_F_AVA
IL’ undeclared (first use in this function); did you mean ‘VRING_DESC_F_WRITE’? 
 387 |  return wrap_counter == !!(desc->flags & VRING_DESC_F_AVAIL) && 
 |  ^~ 
 |  VRING_DESC_F_WRITE 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:387:42:
 note: each undeclared id
entifier is reported only once for each function it appears in
In file included from 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/socket.c:22:
 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:
 In function ‘desc_is_avail’: 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:387:42:
 error: ‘VRING_DESC_F_AVA
IL’ undeclared (first use in this function); did you mean ‘VRING_DESC_F_WRITE’? 
 387 |  return wrap_counter == !!(desc->flags & VRING_DESC_F_AVAIL) && 
 |  ^~ 
 |  VRING_DESC_F_WRITE 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:388:36:
 error: ‘VRING_DESC_F_USE
D’ undeclared (first use in this function); did you mean ‘VRING_DESC_F_NEXT’? 
 388 |   wrap_counter != !!(desc->flags & VRING_DESC_F_USED); 
 |    ^ 
 |    VRING_DESC_F_NEXT 
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:387:42:
 note: each undeclared id
entifier is reported only once for each function it appears in
/home/user/Sources/vpp/src/vpp/build-root/build-vpp-native/external/dpdk-18.08/lib/librte_vhost/vhost.h:388:36:
 error: ‘VRING_DESC_F_USE
D’ undeclared (first use in this function); did you mean ‘VRING_DESC_F_NEXT’? 
 388 |   wrap_counter !=

Re: [vpp-dev] Project Proposal for uDPI

2019-08-09 Thread Ni, Hongjun 
Hi Alexey,

Could you give some thoughts on this?

Thanks,
Hongjun

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Alexey
Sent: Friday, August 9, 2019 6:54 PM
To: Ni, Hongjun ; t...@lists.fd.io
Cc: vpp-dev@lists.fd.io; Wang, Xiang W ; Hong, Yang A 
; Chang, Harry ; 
gu.ji...@zte.com.cn; Shan Jianghua ; Zhang Yang 
; Li Xingfu ; Wu Shuai 
; Xia Yuying ; Fan Chenggang 
; Gao Feng ; Liu Zhong 
; Zhao Yong ; Chen Haiquan 

Subject: Re: [vpp-dev] Project Proposal for uDPI

udpi is died


09.08.2019, 04:11, "Ni, Hongjun" 
mailto:hongjun...@intel.com>>:

Hello FD.io TSCs



Please accept this project proposal for uDPI for consideration.

https://wiki.fd.io/view/Project_Proposals/uDPI



So far, this project has 11 founders and 15 initial committers from

Intel, ZTE, China Telecom, HuachenTel, Inspur, Yxlink, Sunyainfo, Tencent, 
China Unicom, Huawei, QingCloud.



If possible, I would like to present this on TSC meeting.



Thanks,

Hongjun
,

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13684): https://lists.fd.io/g/vpp-dev/message/13684
Mute This Topic: https://lists.fd.io/mt/32805807/675634
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
[devel-net-ne-vleza...@yandex.ru]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13699): https://lists.fd.io/g/vpp-dev/message/13699
Mute This Topic: https://lists.fd.io/mt/32805807/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] a question about route del,thanks

2019-08-09 Thread Neale Ranns via Lists.Fd.Io 

The FIB is a shared resource and each user of that shared resource needs to be 
managed so they don’t interfere with one another. Different users are termed 
‘sources’. FIB treats the API and CLI as separate ‘sources’ of routes. One 
source cannot delete the state (routes nor paths) added by another. So for 
example a route added by BGP through the API cannot be removed by plugin X.

I would also suggest you talk briefly with the sweetcomb team to ask them 
whether simultaneous programming via sweetcomb and CLI is supported.

/neale


De :  au nom de "dengxun...@163.com" 
Date : vendredi 9 août 2019 à 14:32
À : "vpp-dev@lists.fd.io" 
Objet : Re: [vpp-dev] a question about route del,thanks

yes, my question is can i use cli delete routes that create via c api?
i add these routes though sweetcomb, another project of fd.io, actually is 
though c api.

in my mind, cli, c api operate the same object, why can't i delete routes that 
create via api, by using vpp cli ?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13698): https://lists.fd.io/g/vpp-dev/message/13698
Mute This Topic: https://lists.fd.io/mt/32808502/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Arch linux buildd problem

2019-08-09 Thread Benoit Ganne (bganne) via Lists.Fd.Io 
Looks like gcc 9 started to enforce the use of -maes compile switch for AES 
builtins use.
You can try https://gerrit.fd.io/r/c/vpp/+/21191

ben

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Alexey
> Sent: vendredi 9 août 2019 10:43
> To: vpp-dev 
> Subject: [vpp-dev] Arch linux buildd problem
> 
> GCC 9.2
> Platform: archlinux
> 
> VPP version : 20.01-rc0~1-gf16826e7b
> VPP library version : 20.01
> GIT toplevel dir: /home/user/Sources/vpp
> Build type  :
> C flags : -Wno-address-of-packed-member -march=corei7 -
> mtune=corei7-avx -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-protector
> -fPIC -Wall -Werror -fno-common
> Linker flags: -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-
> protector -fPIC -Wall -Werror -fno-common
> Host processor  : x86_64
> Target processor: x86_64
> Prefix path :
> /opt/vpp/external/x86_64;/home/user/Sources/vpp/build-root/install-
> vpp_debug-native/external
> Install prefix  : /home/user/Sources/vpp/build-root/install-vpp_debug-
> native/vpp
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /home/user/Sources/vpp/build-
> root/build-vpp_debug-native/vpp
>  Building vpp in /home/user/Sources/vpp/build-root/build-vpp_debug-
> native/vpp 
> [1/734] Building C object
> plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o
> FAILED: plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o
> /usr/bin/cc -DHAVE_GETCPU -DHAVE_MEMFD_CREATE -I/home/user/Sources/vpp/src
> -I. -Iinclude -I/home/user/Sources/vpp/src/plugins -Iplugins -Wno-address-
> of-packed-member -march=corei7 -mtune=corei7-avx -O0 -DCLIB_DEBUG -g -
> DFORTIFY_SOURCE=2 -fstack-protector -fPIC -Wall -Werror -fno-common -fPIC
> -march=silvermont -Wall -fno-common -MD -MT
> plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o -MF
> plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o.d -o
> plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o   -c
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c
> In file included from /usr/lib/gcc/x86_64-pc-linux-
> gnu/9.1.0/include/immintrin.h:39,
>  from /usr/lib/gcc/x86_64-pc-linux-
> gnu/9.1.0/include/x86intrin.h:32,
>  from
> /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
>  from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
>  from /home/user/Sources/vpp/src/vppinfra/string.h:48,
>  from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
>  from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
>  from /home/user/Sources/vpp/src/vppinfra/format.h:44,
>  from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
>  from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
>  from /home/user/Sources/vpp/src/vlib/vlib.h:44,
>  from
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h: В функции
> «aes_key_enc_to_dec»:
> /usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка:
> inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не
> выполнена: target specific option mismatch
>77 | _mm_aesimc_si128 (__m128i __X)
>   | ^~~~
> In file included from
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:212:14: замечание:
> которая вызвана здесь
>   212 |   k[i] = _mm_aesimc_si128 (r);
>   |  ^~~~
> In file included from /usr/lib/gcc/x86_64-pc-linux-
> gnu/9.1.0/include/immintrin.h:39,
>  from /usr/lib/gcc/x86_64-pc-linux-
> gnu/9.1.0/include/x86intrin.h:32,
>  from
> /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
>  from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
>  from /home/user/Sources/vpp/src/vppinfra/string.h:48,
>  from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
>  from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
>  from /home/user/Sources/vpp/src/vppinfra/format.h:44,
>  from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
>  from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
>  from /home/user/Sources/vpp/src/vlib/vlib.h:44,
>  from
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
> /usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка:
> inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не
> выполнена: target specific option mismatch
>77 | _mm_aesimc_si128 (__m128i __X)
>   | ^~~~
> In file included from
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
> /home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:211:23:

Re: [vpp-dev] a question about route del,thanks

2019-08-09 Thread dengxunaaa 
yes, my question is can i use cli delete routes that create via c api?
i add these routes though sweetcomb, another project of fd.io, actually is 
though c api.

in my mind, cli, c api operate the same object, why can't i delete routes that 
create via api, by using vpp cli ?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13696): https://lists.fd.io/g/vpp-dev/message/13696
Mute This Topic: https://lists.fd.io/mt/32808502/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Can VPP detect illegal packet size?

2019-08-09 Thread Dave Barach via Lists.Fd.Io 
Are you referring to checks of the form “ip-length <= L2 length,” which happen 
in .../src/vnet/ip/ip[46]_input.c?

From: vpp-dev@lists.fd.io  On Behalf Of kmp...@soosan.co.kr
Sent: Friday, August 9, 2019 7:24 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Can VPP detect illegal packet size?


Hi


I wonder that how VPP detect illegal packet length. I couldn't find in dpdk and 
unix/tap, ethernet, ipv4/6 source codes.

Linux uses 'pskb_may_pull' function to detect wrong packets whereas VPP does 
not use 'vlib_buffer_pull' like functions.

Why VPP does not check the length of received packets?
Does It guarantee to access the packet's data which has wrong size?

Thanks.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13695): https://lists.fd.io/g/vpp-dev/message/13695
Mute This Topic: https://lists.fd.io/mt/32809362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Can VPP detect illegal packet size?

2019-08-09 Thread kmpark 
HiI wonder that how VPP detect illegal packet length. I couldn't find in dpdk and unix/tap, ethernet, ipv4/6 source codes.Linux uses 'pskb_may_pull' function to detect wrong packets whereas VPP does not use 'vlib_buffer_pull' like functions.Why VPP does not check the length of received packets?Does It guarantee to access the packet's data which has wrong size?Thanks.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13694): https://lists.fd.io/g/vpp-dev/message/13694
Mute This Topic: https://lists.fd.io/mt/32809362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Project Proposal for uDPI

2019-08-09 Thread Alexey 
udpi is died09.08.2019, 04:11, "Ni, Hongjun" :

Hello FD.io TSCs
 
Please accept this project proposal for uDPI for consideration.
https://wiki.fd.io/view/Project_Proposals/uDPI
 
So far, this project has 11 founders and 15 initial committers from
Intel, ZTE, China Telecom, HuachenTel, Inspur, Yxlink, Sunyainfo, Tencent, China Unicom, Huawei, QingCloud.
 
If possible, I would like to present this on TSC meeting.
 
Thanks,
Hongjun


,-=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.View/Reply Online (#13684): https://lists.fd.io/g/vpp-dev/message/13684Mute This Topic: https://lists.fd.io/mt/32805807/675634Group Owner: vpp-dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [devel-net-ne-vleza...@yandex.ru]-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13693): https://lists.fd.io/g/vpp-dev/message/13693
Mute This Topic: https://lists.fd.io/mt/32805807/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] a question about route del,thanks

2019-08-09 Thread Neale Ranns via Lists.Fd.Io 

Hi,

I don’t really understand what you’re asking, but if the question is, can I 
delete routes via the CLI that I add via the API, the answer is no (nor 
vice-versa).

/neale


De :  au nom de "dengxun...@163.com" 
Date : vendredi 9 août 2019 à 10:33
À : "vpp-dev@lists.fd.io" 
Objet : [vpp-dev] a question about route del,thanks

i have add route through netconf,15.1.1.0/24 via 1.0.0.9，but i can‘t 
delete it by the cmd  ip route del 15.1.1.0/24.
when i exec show ip fib, there is a entry below.  But i can delete the route 
created by cmd.
i want to know What could be the reason for this situation? does somebody 
encountered a similar problem?

15.1.1.0/24
  unicast-ip4-chain
  [@0]: dpo-load-balance: [proto:ip4 index:9 buckets:1 uRPF:8 to:[0:0]]
[0] [@0]: dpo-drop ip4

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13692): https://lists.fd.io/g/vpp-dev/message/13692
Mute This Topic: https://lists.fd.io/mt/32808502/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP Client C API

2019-08-09 Thread Christian Hopps 
The Lua thing is a bit sad, as openwrt's luci uses lua. :)

Thanks,
Chris.

> On Aug 9, 2019, at 4:33 AM, Ole Troan  wrote:
> 
> There's also Go, Python, Lua(rotted) and Java bindings.



signature.asc
Description: Message signed with OpenPGP
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13691): https://lists.fd.io/g/vpp-dev/message/13691
Mute This Topic: https://lists.fd.io/mt/32808207/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Arch linux buildd problem

2019-08-09 Thread Alexey 
GCC 9.2
Platform: archlinux 

VPP version : 20.01-rc0~1-gf16826e7b
VPP library version : 20.01
GIT toplevel dir: /home/user/Sources/vpp
Build type  : 
C flags : -Wno-address-of-packed-member -march=corei7 
-mtune=corei7-avx -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-protector 
-fPIC -Wall -Werror -fno-common
Linker flags: -O0 -DCLIB_DEBUG -g -DFORTIFY_SOURCE=2 -fstack-protector 
-fPIC -Wall -Werror -fno-common
Host processor  : x86_64
Target processor: x86_64
Prefix path : 
/opt/vpp/external/x86_64;/home/user/Sources/vpp/build-root/install-vpp_debug-native/external
Install prefix  : 
/home/user/Sources/vpp/build-root/install-vpp_debug-native/vpp
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/user/Sources/vpp/build-root/build-vpp_debug-native/vpp
 Building vpp in 
/home/user/Sources/vpp/build-root/build-vpp_debug-native/vpp 
[1/734] Building C object 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o
FAILED: plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o 
/usr/bin/cc -DHAVE_GETCPU -DHAVE_MEMFD_CREATE -I/home/user/Sources/vpp/src -I. 
-Iinclude -I/home/user/Sources/vpp/src/plugins -Iplugins 
-Wno-address-of-packed-member -march=corei7 -mtune=corei7-avx -O0 -DCLIB_DEBUG 
-g -DFORTIFY_SOURCE=2 -fstack-protector -fPIC -Wall -Werror -fno-common -fPIC   
-march=silvermont -Wall -fno-common -MD -MT 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o -MF 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o.d -o 
plugins/crypto_ia32/CMakeFiles/crypto_ia32_sse42.dir/aes_cbc.c.o   -c 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
 from /home/user/Sources/vpp/src/vppinfra/string.h:48,
 from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
 from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
 from /home/user/Sources/vpp/src/vppinfra/format.h:44,
 from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
 from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
 from /home/user/Sources/vpp/src/vlib/vlib.h:44,
 from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h: В функции 
«aes_key_enc_to_dec»:
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка: 
inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не 
выполнена: target specific option mismatch
   77 | _mm_aesimc_si128 (__m128i __X)
  | ^~~~
In file included from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:212:14: замечание: 
которая вызвана здесь
  212 |   k[i] = _mm_aesimc_si128 (r);
  |  ^~~~
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,
 from /home/user/Sources/vpp/src/vppinfra/string.h:48,
 from /home/user/Sources/vpp/src/vppinfra/mem.h:55,
 from /home/user/Sources/vpp/src/vppinfra/vec.h:42,
 from /home/user/Sources/vpp/src/vppinfra/format.h:44,
 from /home/user/Sources/vpp/src/vppinfra/elf.h:41,
 from /home/user/Sources/vpp/src/vppinfra/elf_clib.h:41,
 from /home/user/Sources/vpp/src/vlib/vlib.h:44,
 from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:18:
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/wmmintrin.h:77:1: ошибка: 
inline-подстановка для вызова always_inline функции «_mm_aesimc_si128» не 
выполнена: target specific option mismatch
   77 | _mm_aesimc_si128 (__m128i __X)
  | ^~~~
In file included from 
/home/user/Sources/vpp/src/plugins/crypto_ia32/aes_cbc.c:23:
/home/user/Sources/vpp/src/plugins/crypto_ia32/aesni.h:211:23: замечание: 
которая вызвана здесь
  211 |   k[rounds - i] = _mm_aesimc_si128 (k[i]);
  |   ^~~
In file included from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/immintrin.h:39,
 from 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/include/x86intrin.h:32,
 from /home/user/Sources/vpp/src/vppinfra/vector_sse42.h:42,
 from /home/user/Sources/vpp/src/vppinfra/vector.h:162,

[vpp-dev] a question about route del,thanks

2019-08-09 Thread dengxunaaa 
i have add route through netconf,        15.1.1.0/24 via 1.0.0.9，but i can‘t 
delete it by the cmd      ip route del 15.1.1.0/24.
when i exec show ip fib, there is a entry below.  But i can delete the route 
created by cmd.

i want to know What could be the reason for this situation? does somebody 
encountered a similar problem?

15.1.1.0/24
unicast-ip4-chain
[@0]: dpo-load-balance: [proto:ip4 index:9 buckets:1 uRPF:8 to:[0:0]]
[0] [@0]: dpo-drop ip4
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13688): https://lists.fd.io/g/vpp-dev/message/13688
Mute This Topic: https://lists.fd.io/mt/32808502/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Trouble with checkstyle?

2019-08-09 Thread Damjan Marion via Lists.Fd.Io 
Are you using ubuntu 19.04 or some other recent distro with new version of gnu 
indent?

After many years they released new version with lot of bug fixes. We use old 
version with many bugs, and our repo is full of products of those bugs like the 
one you pasted bellow...

— 
Damjan

> On 9 Aug 2019, at 04:50, Jim Thompson via Lists.Fd.Io 
>  wrote:
> 
> So I’ve got this tiny patch to add a couple QAT PCIe IDs:
> 
> But when I run checkstyle.sh, it moans, and wants me to run indent twice.
> 
> Here’s the thing, the only thing that’s changed by the indent is the ELOG 
> statements.
> The little piece I tried to add is unchanged, but checkstyle.sh passes 
> without my change to add the PCIe IDs for c4xxx and d15xx QAT.
> 
> Is this a bug in checkstyle?
> 
> Should I just go ahead and submit the below, or should I attempt to submit 
> just the part that adds PCIe IDs for the two missing QAT VFs?
> 
> Jim
> 
> jim@sharktank-01:~/vpp$ git diff
> diff --git a/src/plugins/dpdk/device/init.c b/src/plugins/dpdk/device/init.c
> index 07cbbf997..5f4cda8fd 100644
> --- a/src/plugins/dpdk/device/init.c
> +++ b/src/plugins/dpdk/device/init.c
> @@ -915,7 +915,8 @@ dpdk_bind_devices_to_uio (dpdk_config_main_t * conf)
>   ;
> /* all Intel QAT devices VFs */
> else if (d->vendor_id == 0x8086 && d->device_class == 
> PCI_CLASS_PROCESSOR_CO &&
> -(d->device_id == 0x0443 || d->device_id == 0x37c9 || d->device_id == 
> 0x19e3))
> +(d->device_id == 0x0443 || d->device_id == 0x18a1 || d->device_id == 
> 0x19e3 || d->device_id == 0x37c9 ||
> +d->device_id == 0x6f55))
>   ;
> /* Cisco VIC */
> else if (d->vendor_id == 0x1137 &&
> @@ -1483,11 +1484,11 @@ dpdk_update_link_state (dpdk_device_t * xd, f64 now)
>   if (LINK_STATE_ELOGS)
> {
>   vlib_main_t *vm = vlib_get_main ();
> -  ELOG_TYPE_DECLARE (e) =
> -  {
> -  .format =
> +  ELOG_TYPE_DECLARE (e) = {
> +   .format =
>  "update-link-state: sw_if_index %d, admin_up %d,"
> - "old link_state %d new link_state %d",.format_args = "i4i1i1i1",};
> + "old link_state %d new link_state %d",.format_args = "i4i1i1i1",
> +  };
> 
>   struct
>   {
> @@ -1537,11 +1538,11 @@ dpdk_update_link_state (dpdk_device_t * xd, f64 now)
>{
>  vlib_main_t *vm = vlib_get_main ();
> 
> - ELOG_TYPE_DECLARE (e) =
> - {
> - .format =
> + ELOG_TYPE_DECLARE (e) = {
> +   .format =
>  "update-link-state: sw_if_index %d, new flags %d",.format_args
> - = "i4i4",};
> + = "i4i4",
> + };
> 
>  struct
>  {
> jim@sharktank-01:~/vpp$
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#13685): https://lists.fd.io/g/vpp-dev/message/13685
> Mute This Topic: https://lists.fd.io/mt/32806741/675642
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13687): https://lists.fd.io/g/vpp-dev/message/13687
Mute This Topic: https://lists.fd.io/mt/32806741/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Client C API

2019-08-09 Thread Hua Lv 
Hi VPP team,

Here’s a basic question for the VPP APIs. We are trying to integrate the VPP 
into our application. We plan to use the C API as the interface between our 
software and VPP.  I thought there was a C library that can be built into our 
software at least for existing plugins. Unfortunately I didn’t find it. The 
only thing I got is the vat.  Do I have to write such a library by ourselves?

Thanks.

Hua.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13686): https://lists.fd.io/g/vpp-dev/message/13686
Mute This Topic: https://lists.fd.io/mt/32808207/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-