Re: [vpp-dev] About Risc-V Porting
Hi Damjan, I upgraded my Unmatched board to run Ubuntu 21.10 from 21.04. I was able to build VPP on Unmatched. I am also trying to build it on Qemu with GCC 10. I am getting following error, ubuntu@ubuntu:~/work/vpp$ make build make[1]: Entering directory '/home/ubuntu/work/vpp/build-root' Arch for platform 'vpp' is native Finding source for external Makefile fragment found in /home/ubuntu/work/vpp/build-data/packages/ external.mk Source found in /home/ubuntu/work/vpp/build Arch for platform 'vpp' is native Finding source for vpp Makefile fragment found in /home/ubuntu/work/vpp/build-data/packages/ vpp.mk Source found in /home/ubuntu/work/vpp/src find: ‘/home/ubuntu/work/vpp/build-root/config.site’: No such file or directory Configuring external: nothing to do Building external: nothing to do Installing external: nothing to do find: ‘/home/ubuntu/work/vpp/build-root/config.site’: No such file or directory Configuring vpp: nothing to do Building vpp in /home/ubuntu/work/vpp/build-root/build-vpp_debug-native/vpp [2/1463] Linking C executable bin/svmtool FAILED: bin/svmtool : && ccache /usr/lib/ccache/gcc-10 CMakeFiles/svm/CMakeFiles/svmtool.dir/svmtool.c.o -o bin/svmtool -Wl,-rpath,/home/ubuntu/work/vpp/build-root/build-vpp_debug-native/vpp/lib/riscv64-linux-gnu:: lib/riscv64-linux-gnu/libsvm.so.22.02 lib/riscv64-linux-gnu/libvppinfra.so.22.02 -lm -lrt -lpthread && : /usr/bin/ld: lib/riscv64-linux-gnu/libvppinfra.so.22.02: undefined reference to `__atomic_exchange_1' collect2: error: ld returned 1 exit status [3/1463] Linking C executable bin/svmdbtool FAILED: bin/svmdbtool : && ccache /usr/lib/ccache/gcc-10 CMakeFiles/svm/CMakeFiles/svmdbtool.dir/svmdbtool.c.o -o bin/svmdbtool -Wl,-rpath,/home/ubuntu/work/vpp/build-root/build-vpp_debug-native/vpp/lib/riscv64-linux-gnu:: lib/riscv64-linux-gnu/libsvmdb.so.22.02 lib/riscv64-linux-gnu/libsvm.so.22.02 lib/riscv64-linux-gnu/libvppinfra.so.22.02 -lm -lrt -lpthread && : /usr/bin/ld: lib/riscv64-linux-gnu/libvppinfra.so.22.02: undefined reference to `__atomic_exchange_1' collect2: error: ld returned 1 exit status [5/1463] Building C object CMakeFiles/vlib/CMakeFiles/vlib_objs.dir/drop.c.o ninja: build stopped: subcommand failed. make[1]: *** [Makefile:693: vpp-build] Error 1 make[1]: Leaving directory '/home/ubuntu/work/vpp/build-root' make: *** [Makefile:356: build] Error 2 Libatomic is present on my machine. Can you give me some pointers to resolve the same? Thanks, Hrishikesh On Mon, Nov 8, 2021 at 8:19 PM Hrishikesh Karanjikar < hrishikesh.karanji...@gmail.com> wrote: > Hi, > > This is great. > Thanks a lot. > Let me try that. > > Hrishikesh > > On Mon, Nov 8, 2021 at 8:00 PM Damjan Marion wrote: > >> I compiled directly on the Unmatched board. I also submitted series of >> patches which are fixing all >> issues you are referring to. >> >> you can use both clang and gcc, problem with clang is that some parts of >> VPP unconditionally turn address sanitiser on and there is no ASAN >> shared libraries available for risc-v. >> You can bypass this temporarely by commenting out test_pnat, test_vat and >> test_vat2 targets. >> >> I also managed to cross-compile vpp on ubuntu system by using debian >> multiarch libs. >> >> # dpkg --add-architecture riscv64 >> >> Update sources.list: >> >> deb [arch=arm64,armhf,riscv64] http://ports.ubuntu.com/ubuntu-ports/ >> impish main restricted universe multiverse >> deb [arch=arm64,armhf,riscv64] http://ports.ubuntu.com/ubuntu-ports/ >> impish-updates main restricted universe multiverse >> deb [arch=arm64,armhf,riscv64] http://ports.ubuntu.com/ubuntu-ports/ >> impish-backports main restricted universe multiverse >> >> # apt update >> >> # apt install crossbuild-essential-riscv64 libssl-dev:riscv64 >> uuid-dev:riscv64 libnl-3-dev:riscv6 libnl-route-3-dev:riscv64 >> libbpf-dev:riscv64 >> >> >> $ cmake \ >> -DCMAKE_SYSTEM_NAME=Linux \ >> -DCMAKE_SYSTEM_PROCESSOR=riscv64 \ >> -DCMAKE_C_COMPILER=riscv64-linux-gnu-gcc \ >> -DCMAKE_CXX_COMPILER=riscv64-linux-gnu-gcc \ >> -DCMAKE_C_COMPILER_TARGET=riscv64-linux-gnu \ >> -DCMAKE_CXX_COMPILER_TARGET=riscv64-linux-gnu \ >> -DCMAKE_ASM_COMPILER_TARGET=riscv64-linux-gnu \ >> -DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM=NEVER \ >> -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY=BOTH \ >> -DCMAKE_FIND_ROOT_PATH_MODE_INCLUDE=BOTH \ >> -DCMAKE_FIND_ROOT_PATH_MODE_PACKAGE=ONLY \ >> -DCMAKE_FIND_ROOT_PATH=/usr/riscv64-linux-gnu \ >> -DCMAKE_INSTALL_PREFIX=/usr/local \ >> -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=ON \ >> -DCMAKE_BUILD_TYPE:STRING=debug \ >> -G Ninja \ >> -S src \ >> -B . >> >> $ ninja >> >> $ file bin/vpp >> bin/vpp: ELF 64-bit LSB
Re: [vpp-dev] project call
Excellent idea. I think having a rigid agenda discourages participation. Also, the scheduling of the call caused me to learn of some features of iOS calendar…. I thought it would be good to have it a weekly half-hour or so occurrence, with a possible early finish; but biweekly is the step in that direction ! :-) +1 on everything you wrote. --a > On 9 Nov 2021, at 17:20, Damjan Marion via lists.fd.io > wrote: > > > Today on the project call, we were discussing about doing some changes on > those calls. > > Proposal from few of us who were attending is: > > - we should make it less formal, stop doing readouts and focus on specific > topics to discuss, if there is no topics to discuss we simply drop > > - we move to biweekly, same time, 2nd and 4th Tue each month > > - to increase attendance we encourage people having something to discuss to > announce that in advance on the mailing list > > - we should preferably use this mailing list if we need to make any decisions > > > What other people think? > > Thanks, > > — > Damjan > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20472): https://lists.fd.io/g/vpp-dev/message/20472 Mute This Topic: https://lists.fd.io/mt/86936610/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 call
+1 > On Nov 9, 2021, at 9:20 AM, Damjan Marion via lists.fd.io > wrote: > > > Today on the project call, we were discussing about doing some changes on > those calls. > > Proposal from few of us who were attending is: > > - we should make it less formal, stop doing readouts and focus on specific > topics to discuss, if there is no topics to discuss we simply drop > > - we move to biweekly, same time, 2nd and 4th Tue each month > > - to increase attendance we encourage people having something to discuss to > announce that in advance on the mailing list > > - we should preferably use this mailing list if we need to make any decisions > > > What other people think? > > Thanks, > > — > Damjan > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20471): https://lists.fd.io/g/vpp-dev/message/20471 Mute This Topic: https://lists.fd.io/mt/86936610/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] FD.io - OpenStack Cloud Issue
This issue has been resolved. If you have any other issues, please open a ticket at support.linuxfoundation.org Thank you, Vanessa On 11/9/21 2:06 PM, Vanessa Valderrama wrote: We are currently experiencing issues spinning up OpenStack executors due to an outage with our provider. This issue is impacting all projects. Our provider is treating this as a high priority. Thank you, Vanessa -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20470): https://lists.fd.io/g/vpp-dev/message/20470 Mute This Topic: https://lists.fd.io/mt/86940702/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] FD.io - OpenStack Cloud Issue
We are currently experiencing issues spinning up OpenStack executors due to an outage with our provider. This issue is impacting all projects. Our provider is treating this as a high priority. Thank you, Vanessa -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20469): https://lists.fd.io/g/vpp-dev/message/20469 Mute This Topic: https://lists.fd.io/mt/86940702/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V Porting)
Thanks ben, Inline please, On Tue, 9 Nov, 2021, 7:24 pm Benoit Ganne (bganne) via lists.fd.io, wrote: > Hi Ben, > > DPDK is definitely supported in VPP but it has performance impacts In case, we have performance bench marking, please share with us. and also carries a lot of dependencies (see for example the discussion on > RISC-V: if DPDK was mandatory, we'd have to have both DPDK and VPP on > RISC-V, but as VPP have native drivers too, we can get away without DPDK). > Nice, please share wiki link, I sm not aware about that, VPP currently have native drivers for the following physical NICs: > - avf: Intel with AVF support (Fortville and Columbiaville) > - rdma: Mellanox mlx5 (ConnectX-4/5/6) > In case, the support are, please share wiki link, Thanks for details //MJ > Best > ben > > > -Original Message- > > From: vpp-dev@lists.fd.io On Behalf Of Ben > McKeegan > > Sent: mardi 9 novembre 2021 11:38 > > To: vpp-dev@lists.fd.io > > Subject: Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V > > Porting) > > > > Hi, > > > > On 08/11/2021 19:15, Damjan Marion via lists.fd.io wrote: > > > > > > and that VPP works better when DPDK is not involved. > > > > > > > > > Apologies for hijacking the thread but as a new VPP user who has spent > > many many hours reading through every scrap of documentation I can find, > > this statement comes as a surprise to me. Unfortunately a lot of the > > VPP documentation seems a bit out of date. Indeed, the documentation > > for most the recent release still says it 'Leverages best-of-breed open > > source driver technology: DPDK': > > > > https://s3-docs.fd.io/vpp/21.10/whatisvpp/performance.html > > > > So if DPDK isn't the best option any more, what do the people of this > > list recommend as a NIC and driver combination, and why? > > (Unfortunately, I don't have a huge budget at my disposal, so I'm > > looking for some best value-for-money options.) > > > > Thanks, > > Ben. > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20468): https://lists.fd.io/g/vpp-dev/message/20468 Mute This Topic: https://lists.fd.io/mt/86928356/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 call
+1 On Tue, Nov 9, 2021 at 11:20 AM Damjan Marion via lists.fd.io wrote: > > Today on the project call, we were discussing about doing some changes on > those calls. > > Proposal from few of us who were attending is: > > - we should make it less formal, stop doing readouts and focus on specific > topics to discuss, if there is no topics to discuss we simply drop > > - we move to biweekly, same time, 2nd and 4th Tue each month > > - to increase attendance we encourage people having something to discuss > to announce that in advance on the mailing list > > - we should preferably use this mailing list if we need to make any > decisions > > > What other people think? > > Thanks, > > — > Damjan > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20467): https://lists.fd.io/g/vpp-dev/message/20467 Mute This Topic: https://lists.fd.io/mt/86936610/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] older issues still affecting CSIT
Hello, this is part two of what I had prepared for VPP monthly meeting. Older VPP Jira tickets: - https://jira.fd.io/browse/VPP-1972 (Regression in NAT44ed performance) There might be multiple additional regressions, either in performance or in memory usage, affecting NAT tests. Example trending page: https://s3-docs.fd.io/csit/master/trending/trending/nat44-ed-udp-cps-2n-skx-xxv710.html We stopped running the maximum scale test (those with h262144-p63-s16515072 in name) to avoid failures and long test durations. - https://jira.fd.io/browse/VPP-1947 (Simpler processing is less efficient with more workers) Affects "Speedup Multi-Core" report graphs (see the link in the first Jira comment). CSIT Jira tickets (probably driver issues) VPP developers may help fix: - https://jira.fd.io/browse/CSIT-1791 (Performance regression in RDMA tests) Two symptoms, present since we upgraded CSIT machines to Ubuntu 20.04. - https://jira.fd.io/browse/CSIT-1782 (4c AVF tests are failing when trying to create interface) Occasionally present despite a CSIT workaround. Vratko. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20464): https://lists.fd.io/g/vpp-dev/message/20464 Mute This Topic: https://lists.fd.io/mt/86935620/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] create environment of IPsec Acceleration in the FD.io* VPP Project
Hi, I'm trying to create environment of IPsec Acceleration in the FD.io* VPP Project shown as following instruction. https://www.intel.com/content/www/us/en/developer/articles/guide/get-started-with-ipsec-acceleration-in-the-fdio-vpp-project.html If anyone has done intel's instruction, that will grate. I would like to hear your environment (such as Operation System, or else). Currently I'm using Ubuntu 16.04.7 LTS, but if any other OS will works correctly, I can change it. When I execute following, the error had occurred. $ vpp_uses_dpdk_cryptodev_sw = yes make build - release - j Error Message. CCLD libsixrd_plugin.la /usr/bin/ld: /../vpp/build-root/install-vpp-native/dpdk/lib/libisal_crypto.a(gcm_pre.o): relocation R_X86_64_PC32 against undefined symbol `__stack_chk_fail@@GLIBC_2.4' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:1439: recipe for target 'dpdk_plugin.la' failed make[5]: *** [dpdk_plugin.la] Error 1 make[5]: *** Waiting for unfinished jobs make[5]: Leaving directory '/../test2/vpp/build-root/build-vpp-native/vpp/plugins' Makefile:1265: recipe for target 'all' failed make[4]: *** [all] Error 2 make[4]: Leaving directory '/../vpp/build-root/build-vpp-native/vpp/plugins' Makefile:6765: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/../vpp/build-root/build-vpp-native/vpp' Makefile:3427: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/../vpp/build-root/build-vpp-native/vpp' Makefile:699: recipe for target 'vpp-build' failed make[1]: *** [vpp-build] Error 2 make[1]: Leaving directory '/../vpp/build-root' Makefile:213: recipe for target 'build-release' failed make: *** [build-release] Error 2 Regards, -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20462): https://lists.fd.io/g/vpp-dev/message/20462 Mute This Topic: https://lists.fd.io/mt/86931911/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V Porting)
Hi Ben, DPDK is definitely supported in VPP but it has performance impacts and also carries a lot of dependencies (see for example the discussion on RISC-V: if DPDK was mandatory, we'd have to have both DPDK and VPP on RISC-V, but as VPP have native drivers too, we can get away without DPDK). VPP currently have native drivers for the following physical NICs: - avf: Intel with AVF support (Fortville and Columbiaville) - rdma: Mellanox mlx5 (ConnectX-4/5/6) Best ben > -Original Message- > From: vpp-dev@lists.fd.io On Behalf Of Ben McKeegan > Sent: mardi 9 novembre 2021 11:38 > To: vpp-dev@lists.fd.io > Subject: Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V > Porting) > > Hi, > > On 08/11/2021 19:15, Damjan Marion via lists.fd.io wrote: > > > > and that VPP works better when DPDK is not involved. > > > > > Apologies for hijacking the thread but as a new VPP user who has spent > many many hours reading through every scrap of documentation I can find, > this statement comes as a surprise to me. Unfortunately a lot of the > VPP documentation seems a bit out of date. Indeed, the documentation > for most the recent release still says it 'Leverages best-of-breed open > source driver technology: DPDK': > > https://s3-docs.fd.io/vpp/21.10/whatisvpp/performance.html > > So if DPDK isn't the best option any more, what do the people of this > list recommend as a NIC and driver combination, and why? > (Unfortunately, I don't have a huge budget at my disposal, so I'm > looking for some best value-for-money options.) > > Thanks, > Ben. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20461): https://lists.fd.io/g/vpp-dev/message/20461 Mute This Topic: https://lists.fd.io/mt/86928356/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V Porting)
Hi, On 08/11/2021 19:15, Damjan Marion via lists.fd.io wrote: and that VPP works better when DPDK is not involved. Apologies for hijacking the thread but as a new VPP user who has spent many many hours reading through every scrap of documentation I can find, this statement comes as a surprise to me. Unfortunately a lot of the VPP documentation seems a bit out of date. Indeed, the documentation for most the recent release still says it 'Leverages best-of-breed open source driver technology: DPDK': https://s3-docs.fd.io/vpp/21.10/whatisvpp/performance.html So if DPDK isn't the best option any more, what do the people of this list recommend as a NIC and driver combination, and why? (Unfortunately, I don't have a huge budget at my disposal, so I'm looking for some best value-for-money options.) Thanks, Ben. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20460): https://lists.fd.io/g/vpp-dev/message/20460 Mute This Topic: https://lists.fd.io/mt/86928356/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Memif can't link up after admin down
Hello there, I pushed the patch for VPP-1959 and I would be grateful for a review.(The patch contains fix and test.) https://gerrit.fd.io/r/c/vpp/+/34320 Long story short: After command #set interface state memif0/0 down is called vnet_sw_interface_set_flags_helper() where on the end of function is link-up changed to link-down. Unfortunately Admin-up wont link-up the memif interface again. Best regards, Daniel -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20459): https://lists.fd.io/g/vpp-dev/message/20459 Mute This Topic: https://lists.fd.io/mt/86927715/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
