[dpdk-dev] writing app on other that C language
Is that possible to write app not in C , but for example on Go ? Where i can find some docs about api ? -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] dpdk using on network that contains vm traffic and management traffic
Does it possible to use dpdk on eth0/eth1 that provide management network and data network (vm traffic)? -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] unable to compile 1.6.0
Hello. I'm try to create package for my distro for testing, but unable to compile under kvm virtual machine. /proc/cpuinfo processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 2 model name : QEMU Virtual CPU version 1.0 stepping: 3 microcode : 0x1 cpu MHz : 2400.084 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl pni vmx cx16 popcnt hypervisor lahf_lm bogomips: 4800.16 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: error: make config T=x86_64-default-linuxapp-gcc cc1: error: CPU you selected does not support x86-64 instruction set How can i debug this issue? -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] unable to compile 1.6.0
2014-04-25 15:20 GMT+04:00 Neil Horman : > Start by adding V=1 to your command line to start drilling down to where the > problem is actually happening. make -f /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/mk/rte.sdkconfig.mk config if [ "/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/config/defconfig_x86_64-default-linuxapp-gcc" != "" -a -f "/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/config/defconfig_x86_64-default-linuxapp-gcc" ]; then \ cpp -undef -P -x assembler-with-cpp \ -fdirectives-only -ffreestanding \ -o /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/config/defconfig_x86_64-default-linuxapp-gcc ; \ if ! cmp -s /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config; then \ cp /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config ; \ fi ; \ rm -f /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp ; \ else \ echo -n "No template specified. Use T=template " ; \ echo "among the following list:" ; \ for t in x86_64-ivshmem-linuxapp-icc x86_64-ivshmem-linuxapp-gcc i686-default-linuxapp-icc i686-default-linuxapp-gcc x86_64-default-linuxapp-icc x86_64-default-bsdapp-gcc x86_64-default-linuxapp-gcc; do \ echo " $t" ; \ done ; \ fi /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/scripts/gen-build-mk.sh ../ build \ > /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/Makefile rm -rf /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/include /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/app \ /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/hostapp /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/lib \ /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/hostlib /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/kmod /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/build /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/scripts/gen-config-h.sh /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config \ > /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/include/rte_config.h make depdirs make -f /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/mk/rte.sdkdepdirs.mk depdirs make -j3 -j3 V=1 config T=x86_64-default-linuxapp-gcc As i see V=1 not passed down to other makefiles. -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] unable to compile 1.6.0
2014-04-25 16:22 GMT+04:00 Ananyev, Konstantin : > Hi Vasiliy, > Why just not use ' -cpu host' when starting your kvm? Because in this case compiled binaries may use extensions that not supported on other platforms. As i see error happen with MACHINE_CFLAGS = -march=native, but i compile all software with match=x86_64 for compat. -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] unable to compile 1.6.0
2014-04-25 18:02 GMT+04:00 Paul Barrette : > In qemu you can turn off the cpu features that you don't want enabled: > http://www.linux-kvm.org/page/Tuning_KVM > maybe -cpu Nehalem ... Why dpdk not use provided CFLAGS? I think that compile for native arch not best option for packaging stuff for various distributions. Because this is not portable across user systems. -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] unable to compile 1.6.0
2014-04-25 17:03 GMT+04:00 Ananyev, Konstantin : > Then I suppose you need to set > CONFIG_RTE_MACHINE="default" > in your config file. Thanks, this is works fine..., but: /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/mk/internal/rte.compile-pre.mk:126: recipe for target 'eal_common_cpuflags.o' failed /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/lib/librte_eal/common/eal_common_cpuflags.c: In function 'rte_cpu_check_supported': /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/lib/librte_eal/common/eal_common_cpuflags.c:253:4: error: 'RTE_COMPILE_TIME_CPUFLAGS' undeclared (first use in this function) RTE_COMPILE_TIME_CPUFLAGS Why this happening? -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] mellanox connectx-2 support
Hello. I have some mellanox (ConnectX-2 ?) cards (MT26428) does it possible to use it with dpdk? Why dpdk supports only X-4 and X-5 cards? Thanks! -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru
Re: [dpdk-dev] mellanox connectx-2 support
чт, 17 мая 2018 г. в 9:02, Olga Shern : > Vasily, > > ConnectX-2 is very, very old card. > We don't support it. > You can run DPDK on ConnectX-3 Pro, ConnectX-4 /LX and ConnectX-5 NICs. > The best performance and better feature set you will get with ConnectX-5 > > Best Regards, > Thanks for info, web page says about connect-x3 (without pro) If i have Connect-X3 vpi does it works with intel dpdk mellanox driver? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru
Re: [dpdk-dev] mellanox connectx-2 support
пн, 21 мая 2018 г. в 12:15, Adrien Mazarguil : > On Sun, May 20, 2018 at 10:25:01PM +0300, Vasiliy Tolstov wrote: > > чт, 17 мая 2018 г. в 9:02, Olga Shern : > > > > > Vasily, > > > > > > ConnectX-2 is very, very old card. > > > We don't support it. > > > You can run DPDK on ConnectX-3 Pro, ConnectX-4 /LX and ConnectX-5 NICs. > > > The best performance and better feature set you will get with ConnectX-5 > > > > > > Best Regards, > > > > > > > Thanks for info, web page says about connect-x3 (without pro) If i have > > Connect-X3 vpi does it works with intel dpdk mellanox driver? > Probably, provided both an up-to-date firmware version and that ports accept > Ethernet mode configuration [1]. > [1] http://dpdk.org/doc/guides/nics/mlx4.html#quick-start-guide =( Bad news, i need to use rdma to transfer storage traffic and not want to change ports to ethernet. Does dpdk can work with vfio ? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru
Re: [dpdk-dev] mellanox connectx-2 support
вт, 22 мая 2018 г. в 0:17, Olga Shern : > You can use rdma over Ethernet, AKA ROCE As i need to use rdma to storage traffic i don't understand benefits of using ethernet for dpdk and roce for ib over ethernet to storage > Mellanox PMDs don't need vfio > I am not sure what you are trying to achieve, you want to run DPDK on Infiniband? I have node that serve storage traffic via infiniband and wont to switch from IPoIB to dpdk based setup but i don't want to drop infiniband from storage traffic. > -Original Message----- > From: Vasiliy Tolstov [mailto:v.tols...@selfip.ru] > Sent: Tuesday, May 22, 2018 12:10 AM > To: Adrien Mazarguil > Cc: Василий Толстов ; Olga Shern > ; dev@dpdk.org > Subject: Re: [dpdk-dev] mellanox connectx-2 support > пн, 21 мая 2018 г. в 12:15, Adrien Mazarguil : > > On Sun, May 20, 2018 at 10:25:01PM +0300, Vasiliy Tolstov wrote: > > > чт, 17 мая 2018 г. в 9:02, Olga Shern : > > > > > > > Vasily, > > > > > > > > ConnectX-2 is very, very old card. > > > > We don't support it. > > > > You can run DPDK on ConnectX-3 Pro, ConnectX-4 /LX and ConnectX-5 > NICs. > > > > The best performance and better feature set you will get with > ConnectX-5 > > > > > > > > Best Regards, > > > > > > > > > > Thanks for info, web page says about connect-x3 (without pro) If i > > > have > > > Connect-X3 vpi does it works with intel dpdk mellanox driver? > > Probably, provided both an up-to-date firmware version and that ports > accept > > Ethernet mode configuration [1]. > > [1] > > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk > > .org%2Fdoc%2Fguides%2Fnics%2Fmlx4.html%23quick-start-guide&data=02%7C0 > > 1%7Colgas%40mellanox.com%7C01c4e02666044c162d9a08d5bf5f4090%7Ca652971c > > 7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636625338186508009&sdata=doQaWNjEiS > > RhR28TmbS8iGB22oGfnl%2BDVm78fw%2FJTMQ%3D&reserved=0 > =( Bad news, i need to use rdma to transfer storage traffic and not want to change ports to ethernet. > Does dpdk can work with vfio ? > -- > Vasiliy Tolstov, > e-mail: v.tols...@selfip.ru -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru
[dpdk-dev] filtering traffic and forward to os
I'm interesting in dpdk to filter traffic. My use-case - i have server with 10Gbit uplink and i want to add it port via dpdk to ovs, filter traffic and forward it to OS (i need to able to ssh in this port :( ) Does it possible after processing packet in dpdk forward it to kernel ? -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] filtering traffic and forward to os
2015-03-11 15:57 GMT+03:00 Bruce Richardson : > To forward packets from DPDK into kernel, look at the KNI library. (For a more > standard, but lower performing option, TUN/TAP might be an option, see the > exception path example.) Thanks! -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
[dpdk-dev] failed to build latest dpdk 1.8.0 on kvm virtual machine
I'm try to build dpdk 1.8.0
unpack sources
sed -i 's|CONFIG_RTE_MACHINE="native"|CONFIG_RTE_MACHINE="default"|g'
config/defconfig_x86_64-native-linuxapp-gcc
export CFLAGS="-march=core2 -mtune=generic -pipe -O2"
make V=1 config T=x86_64-native-linuxapp-gcc
make V=1 MACHINE_CFLAGS="${CFLAGS}"
/var/tmp/paludis/build/net-dpdk-1.8.0/work/dpdk-1.8.0/mk/internal/rte.compile-pre.mk:126:
recipe for target 'eal_common_cpuflags.o' failed
/var/tmp/paludis/build/net-dpdk-1.8.0/work/dpdk-1.8.0/lib/librte_eal/common/eal_common_cpuflags.c:
In function 'rte_cpu_check_supported':
/var/tmp/paludis/build/net-dpdk-1.8.0/work/dpdk-1.8.0/lib/librte_eal/common/eal_common_cpuflags.c:63:4:
error: 'RTE_COMPILE_TIME_CPUFLAGS' undeclared (first use in this
function)
RTE_COMPILE_TIME_CPUFLAGS
^
--
Vasiliy Tolstov,
e-mail: v.tolstov at selfip.ru
jabber: vase at selfip.ru
[dpdk-dev] failed to build latest dpdk 1.8.0 on kvm virtual machine
2015-03-11 17:14 GMT+03:00 Mcnamara, John : > Hi, > > CFLAGS for DPDK are usually set via EXTRA_CFLAGS. Try the following as a > final set after the other config above: > > EXTRA_CFLAGS="-march=core2 -mtune=generic -pipe -O2" > MACHINE_CFLAGS=$EXTRA_CFLAGS make V=1 > > It compiles DPDK 1.8.0 from source on my test env. Thanks, this works fine. -- Vasiliy Tolstov, e-mail: v.tolstov at selfip.ru jabber: vase at selfip.ru
