Re: Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V Porting)

[Damjan Marion via lists.fd.io]

https://docs.fd.io/csit/master/trending/trending/ip4-2n-clx-xxv710.html#t1c

native AVF driver 22.5 Mpps vs DPDK i40e 17.5Mpps on the same hardware.

Beside what Benoit listed we have following native drivers:
 - virtio
 - vhost-user
 - tap
 - vmxnet
 - memif
 - af_packet
 - af_xdp
 
Ben was right about outdated documentation, contributions in this area are more 
than welcome….

And just to make it clear, I do respect DPDK, it bring lot of traction to 
userspace networking and it is very good fit in many cases.
Problem we have with DPDK is that it is built as monolythic framework and not 
as a set of reusable libraries.
If you want to use NIC drivers you are forced to use buffer management, memory 
allocator, command line parser, and many more.
That makes it very hard to use in existing projects like VPP where we need to 
run lot of DPDK code which is redundant for us just to get some functionality 
working.
It will be really nice that DPDK provides something what rdma-core already 
does, direct access to NIC descriptors so we can only extract data we need 
instead
of copying all data from descriptor to rte_mbuf and then from rte_mbuf to our 
own metadata.
Also in many places we had to write thousands lines of code which sole purpose 
is to cheat DPDK, good example is EAL command line construction or 
fake buffer pools…
As long as DPDK stays as monolithic as it is, our only option is to have native 
drivers….

— 
Damjan



> On 09.11.2021., at 21:05, Mrityunjay Kumar  wrote:
> 
> 
> 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 (#20531): https://lists.fd.io/g/vpp-dev/message/20531
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] About Risc-V Porting

[Hrishikesh Karanjikar]

Hi Damjan,

I am using Ubuntu 20.04 image on Qemu.
I had to do following changes to make it work.

diff --git a/src/vppinfra/CMakeLists.txt b/src/vppinfra/CMakeLists.txt
index 58ec32fbf..2168da185 100644
--- a/src/vppinfra/CMakeLists.txt
+++ b/src/vppinfra/CMakeLists.txt
@@ -219,7 +219,7 @@ if(VPP_USE_EXTERNAL_LIBEXECINFO)
 endif()
 add_vpp_library(vppinfra
   SOURCES ${VPPINFRA_SRCS}
-  LINK_LIBRARIES m ${EXECINFO_LIB}
+  LINK_LIBRARIES m ${EXECINFO_LIB} atomic
   INSTALL_HEADERS ${VPPINFRA_HEADERS}
   COMPONENT libvppinfra
   LTO
ubuntu@ubuntu:~/work/vpp$
ubuntu@ubuntu:~/work/vpp$
ubuntu@ubuntu:~/work/vpp$
ubuntu@ubuntu:~/work/vpp$
ubuntu@ubuntu:~/work/vpp$ uname -a
Linux ubuntu 5.11.0-1022-generic #23~20.04.1-Ubuntu SMP Thu Oct 21 10:16:27
UTC 2021 riscv64 riscv64 riscv64 GNU/Linux
ubuntu@ubuntu:~/work/vpp$

Thanks,
Hrishikesh

On Fri, Nov 12, 2021 at 6:01 PM Damjan Marion  wrote:

>
> Hi,
>
> i tried to repro with gcc-10 on ubuntu 21.10 x86_64 and everything works
> fine.
> Only caveat is that I had to pass -Wno-stringop-overflow in CFLAGS.
>
> —
> Damjan
>
>
>
> On 10.11.2021., at 08:29, Hrishikesh Karanjikar <
> hrishikesh.karanji...@gmail.com> wrote:
>
> 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 

Re: [vpp-dev] About Risc-V Porting

[Damjan Marion via lists.fd.io]

Hi,

i tried to repro with gcc-10 on ubuntu 21.10 x86_64 and everything works fine.
Only caveat is that I had to pass -Wno-stringop-overflow in CFLAGS.

— 
Damjan



> On 10.11.2021., at 08:29, Hrishikesh Karanjikar 
>  wrote:
> 
> 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 
> mailto: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 \
>   

Re: [vpp-dev] About Risc-V Porting

[Hrishikesh Karanjikar]

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: Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V Porting)

[Mrityunjay Kumar]

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: Recommended NICs and drivers (was Re: [vpp-dev] About Risc-V Porting)

[Benoit Ganne (bganne) via lists.fd.io]

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)

[Ben McKeegan]

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]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] About Risc-V Porting

[Mrityunjay Kumar]

Let me close this.

I am not paid by dpdk Or vpp.

It my indivisual thoughts.



Sorry if I *...




On Tue, 9 Nov, 2021, 1:30 am Damjan Marion,  wrote:

>
>
> > On 08.11.2021., at 20:21, Mrityunjay Kumar  wrote:
> >
> > Thank you for the clarification.
> >
> > Inline please,
> >
> >
> >
> >
> > On Tue, 9 Nov, 2021, 12:45 am Damjan Marion,  wrote:
> > >
> > > >
> > > >
> > > >
> > > > On Mon, 8 Nov, 2021, 10:18 pm Damjan Marion via lists.fd.io,
>  wrote:
> > > >
> > > > No, I didn’t bother… Not using DPDK for a long time...
> > >
> > > We know that,
> >
> > Who are “We”?
> >
> > Dpdk users as older than VPP as open source.
>
> DPDK users are not the only people on this list and even if you have
> mandate to represent all of them I don't think you have
> a right to dictate what people are allowed to say on this list.
>
> Also, it is not clear to me why it matters which one is older in
> open-source.
> This sounds to me like “my dad is stronger than yours” kind of
> argumentation.
>
> >
> >
> > >  not required to say, but many of us following DPDK and VPP.
> >
> > I disagree, i think it is important to say as many people is not aware
> that VPP is not DPDK application
> > and that VPP works better when DPDK is not involved.
> >
> > May be, but for me still it's magic,
> >
> >
> > I am saying let have respect of both users.
>
> I absolutely have respect for both users and I didn’t do anything
> disrespectful.
> I simply said that i didn’t bother to compile dpdk as it doesn’t bring any
> value to me.
>
> —
> Damjan
>
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20458): https://lists.fd.io/g/vpp-dev/message/20458
Mute This Topic: https://lists.fd.io/mt/86312689/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] About Risc-V Porting

[Damjan Marion via lists.fd.io]

> On 08.11.2021., at 20:21, Mrityunjay Kumar  wrote:
> 
> Thank you for the clarification. 
> 
> Inline please, 
> 
> 
> 
> 
> On Tue, 9 Nov, 2021, 12:45 am Damjan Marion,  wrote:
> > 
> > > 
> > > 
> > > 
> > > On Mon, 8 Nov, 2021, 10:18 pm Damjan Marion via lists.fd.io, 
> > >  wrote:
> > > 
> > > No, I didn’t bother… Not using DPDK for a long time...
> > 
> > We know that,
> 
> Who are “We”?
> 
> Dpdk users as older than VPP as open source. 

DPDK users are not the only people on this list and even if you have mandate to 
represent all of them I don't think you have 
a right to dictate what people are allowed to say on this list.

Also, it is not clear to me why it matters which one is older in open-source.
This sounds to me like “my dad is stronger than yours” kind of argumentation.

> 
> 
> >  not required to say, but many of us following DPDK and VPP.
> 
> I disagree, i think it is important to say as many people is not aware that 
> VPP is not DPDK application
> and that VPP works better when DPDK is not involved.
> 
> May be, but for me still it's magic,   
> 
> 
> I am saying let have respect of both users. 

I absolutely have respect for both users and I didn’t do anything disrespectful.
I simply said that i didn’t bother to compile dpdk as it doesn’t bring any 
value to me.

— 
Damjan



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20457): https://lists.fd.io/g/vpp-dev/message/20457
Mute This Topic: https://lists.fd.io/mt/86312689/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] About Risc-V Porting

[Mrityunjay Kumar]

Thank you for the clarification.

Inline please,




On Tue, 9 Nov, 2021, 12:45 am Damjan Marion,  wrote:

> >
> > >
> > >
> > >
> > > On Mon, 8 Nov, 2021, 10:18 pm Damjan Marion via lists.fd.io,  me@lists.fd.io> wrote:
> > >
> > > No, I didn’t bother… Not using DPDK for a long time...
> >
> > We know that,
>
> Who are “We”?
>

Dpdk users as older than VPP as open source.


> >  not required to say, but many of us following DPDK and VPP.
>
> I disagree, i think it is important to say as many people is not aware
> that VPP is not DPDK application
> and that VPP works better when DPDK is not involved.
>

May be, but for me still it's magic,


I am saying let have respect of both users.







> >  Let someone reply answer of exact inline question,
>
> Exact question was addressed to me, so please explain how “someone” can
> reply.
>
> —
> Damjan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20456): https://lists.fd.io/g/vpp-dev/message/20456
Mute This Topic: https://lists.fd.io/mt/86312689/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] About Risc-V Porting

[Damjan Marion via lists.fd.io]

> 
> > 
> > 
> > 
> > On Mon, 8 Nov, 2021, 10:18 pm Damjan Marion via lists.fd.io, 
> >  wrote:
> > 
> > No, I didn’t bother… Not using DPDK for a long time...
> 
> We know that,

Who are “We”?

>  not required to say, but many of us following DPDK and VPP.

I disagree, i think it is important to say as many people is not aware that VPP 
is not DPDK application
and that VPP works better when DPDK is not involved.

>  Let someone reply answer of exact inline question, 

Exact question was addressed to me, so please explain how “someone” can reply.

— 
Damjan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20455): https://lists.fd.io/g/vpp-dev/message/20455
Mute This Topic: https://lists.fd.io/mt/86312689/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] About Risc-V Porting

[Mrityunjay Kumar]

Damjan,
Inline,





On Tue, 9 Nov, 2021, 12:03 am Damjan Marion,  wrote:

>
> Sorry, I don’t understand your question.
>
> Are you asking me to forward Hrishikesh’s question if I compiled VPP with
> DPDK on RISC-V5 board to DPDK team?
> How they should know if I compiled VPP with DPDK or not?
>
> Even if it is valid question for dpdk community, I dont feel like I am
> e-mail relay agent.
> Everybody have a freedom to go and ask question on the DPDK mailing list.
>



> —
> Damjan
>
>
>
> > On 08.11.2021., at 19:18, Mrityunjay Kumar  wrote:
> >
> > Damjan, hi again
> >
> > Is it possible to share comunity queries to DPDK team?
> >
> >
> > DPDK: it's self is very big code base.
> >
> > I am only users of both open source. Knowledge exchange are appreciated.
> >
> >
> >
> > /MJ
> >
> >
> >
> >
> > On Mon, 8 Nov, 2021, 10:18 pm Damjan Marion via lists.fd.io,  me@lists.fd.io> wrote:
> >
> > No, I didn’t bother… Not using DPDK for a long time...
>

We know that,  not required to say, but many of us following DPDK and VPP.
Let someone reply answer of exact inline question,




>
> > —
> > Damjan
> >
> >> On 08.11.2021., at 16:51, Hrishikesh Karanjikar <
> hrishikesh.karanji...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> One more thing.
> >> Did you compile with DPDK?
> >> I compiled with DPDK. I have ported DPDK for Risc-V. Not upstreamed yet.
> >> I had to compile without rdma-core.
> >>
> >>
> >>
> >> 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 executable, UCB RISC-V, version 1 (SYSV),
> dynamically linked, interpreter /lib/ld-linux-riscv64-lp64d.so.1,
> BuildID[sha1]=51ac741e44727379a0fbb5936acea4d7b8bdd624, for GNU/Linux
> 4.15.0, with debug_info, not stripped
> >>
> >> And run with qemu:
> >>
> >> $ qemu-riscv64-static ./bin/vpp unix interactive
> >> buffer  [warn  ]: numa[0] falling back to non-hugepage backed
> buffer pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to
> mmap 19 pages at 0x404fc0 fd 4 numa 0 flags 0x11: Invalid argument)
> >> buffer  [warn  ]: numa[1] falling back to non-hugepage backed
> buffer pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to
> set mempolicy for numa node 1: Function not implemented)
> >> vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set
> mempolicy for numa node 1: Function not implementedsvm_queue_init:57:
> mutex_init: No such file or directory (errno 2)
> >> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> >> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> >> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> >> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> >> svm_queue_init:57: 

Re: [vpp-dev] About Risc-V Porting

[Damjan Marion via lists.fd.io]

Sorry, I don’t understand your question.

Are you asking me to forward Hrishikesh’s question if I compiled VPP with DPDK 
on RISC-V5 board to DPDK team?
How they should know if I compiled VPP with DPDK or not?

Even if it is valid question for dpdk community, I dont feel like I am e-mail 
relay agent.
Everybody have a freedom to go and ask question on the DPDK mailing list.

— 
Damjan



> On 08.11.2021., at 19:18, Mrityunjay Kumar  wrote:
> 
> Damjan, hi again
> 
> Is it possible to share comunity queries to DPDK team? 
> 
> 
> DPDK: it's self is very big code base. 
> 
> I am only users of both open source. Knowledge exchange are appreciated. 
> 
> 
> 
> /MJ
> 
> 
> 
> 
> On Mon, 8 Nov, 2021, 10:18 pm Damjan Marion via lists.fd.io, 
>  wrote:
> 
> No, I didn’t bother… Not using DPDK for a long time...
> 
> — 
> Damjan
> 
>> On 08.11.2021., at 16:51, Hrishikesh Karanjikar 
>>  wrote:
>> 
>> Hi,
>> 
>> One more thing.
>> Did you compile with DPDK?
>> I compiled with DPDK. I have ported DPDK for Risc-V. Not upstreamed yet.
>> I had to compile without rdma-core.
>> 
>> 
>> 
>> Thanks,
>> Hrishikesh
>> 
>> On Mon, Nov 8, 2021 at 8:19 PM Hrishikesh Karanjikar 
>>  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 executable, UCB RISC-V, version 1 (SYSV), 
>> dynamically linked, interpreter /lib/ld-linux-riscv64-lp64d.so.1, 
>> BuildID[sha1]=51ac741e44727379a0fbb5936acea4d7b8bdd624, for GNU/Linux 
>> 4.15.0, with debug_info, not stripped
>> 
>> And run with qemu:
>> 
>> $ qemu-riscv64-static ./bin/vpp unix interactive
>> buffer  [warn  ]: numa[0] falling back to non-hugepage backed buffer 
>> pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to mmap 19 
>> pages at 0x404fc0 fd 4 numa 0 flags 0x11: Invalid argument)
>> buffer  [warn  ]: numa[1] falling back to non-hugepage backed buffer 
>> pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set 
>> mempolicy for numa node 1: Function not implemented)
>> vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set mempolicy 
>> for numa node 1: Function not implementedsvm_queue_init:57: mutex_init: No 
>> such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> vat-plug/load  [error ]: vat_plugin_register: oddbuf plugin not loaded...
>> _____   _  ___
>>  __/ __/ _ \  (_)__| | / / _ \/ _ \
>>  _/ _// // / / / _ \   | |/ / ___/ ___/
>>  /_/ /(_)_/\___/   |___/_/  /_/
>> 
>> DBGvpp#
>> 
>> 
>> — 
>> Damjan
>> 
>> 
>> 
>> > On 08.11.2021., at 14:59, 

Re: [vpp-dev] About Risc-V Porting

[Mrityunjay Kumar]

Damjan, hi again

Is it possible to share comunity queries to DPDK team?


DPDK: it's self is very big code base.

I am only users of both open source. Knowledge exchange are appreciated.



/MJ




On Mon, 8 Nov, 2021, 10:18 pm Damjan Marion via lists.fd.io,  wrote:

>
> No, I didn’t bother… Not using DPDK for a long time...
>
> —
> Damjan
>
> On 08.11.2021., at 16:51, Hrishikesh Karanjikar <
> hrishikesh.karanji...@gmail.com> wrote:
>
> Hi,
>
> One more thing.
> Did you compile with DPDK?
> I compiled with DPDK. I have ported DPDK for Risc-V. Not upstreamed yet.
> I had to compile without rdma-core.
>
>
>
> 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 executable, UCB RISC-V, version 1 (SYSV),
>>> dynamically linked, interpreter /lib/ld-linux-riscv64-lp64d.so.1,
>>> BuildID[sha1]=51ac741e44727379a0fbb5936acea4d7b8bdd624, for GNU/Linux
>>> 4.15.0, with debug_info, not stripped
>>>
>>> And run with qemu:
>>>
>>> $ qemu-riscv64-static ./bin/vpp unix interactive
>>> buffer  [warn  ]: numa[0] falling back to non-hugepage backed buffer
>>> pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to mmap 19
>>> pages at 0x404fc0 fd 4 numa 0 flags 0x11: Invalid argument)
>>> buffer  [warn  ]: numa[1] falling back to non-hugepage backed buffer
>>> pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set
>>> mempolicy for numa node 1: Function not implemented)
>>> vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set
>>> mempolicy for numa node 1: Function not implementedsvm_queue_init:57:
>>> mutex_init: No such file or directory (errno 2)
>>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>>> vat-plug/load  [error ]: vat_plugin_register: oddbuf plugin not
>>> loaded...
>>> _____   _  ___
>>>  __/ __/ _ \  (_)__| | / / _ \/ _ \
>>>  _/ _// // / / / _ \   | |/ / ___/ ___/
>>>  /_/ /(_)_/\___/   |___/_/  /_/
>>>
>>> DBGvpp#
>>>
>>>
>>> —
>>> Damjan
>>>
>>>
>>>
>>> > On 08.11.2021., at 14:59, Hrishikesh Karanjikar <
>>> hrishikesh.karanji...@gmail.com> wrote:
>>> >
>>> > Hi,
>>> >
>>> > Thanks for this patch. I will check it out. Which compile did you use?
>>> Did you cross compile or locally compiled it on Qemu or any other platform?
>>> > I was able to compile VPP using GCC10 locally on Qemu but I had to do
>>> other modifications.
>>> > At many places I was able to put 

Re: [vpp-dev] About Risc-V Porting

[Damjan Marion via lists.fd.io]

No, I didn’t bother… Not using DPDK for a long time...

— 
Damjan

> On 08.11.2021., at 16:51, Hrishikesh Karanjikar 
>  wrote:
> 
> Hi,
> 
> One more thing.
> Did you compile with DPDK?
> I compiled with DPDK. I have ported DPDK for Risc-V. Not upstreamed yet.
> I had to compile without rdma-core.
> 
> 
> 
> Thanks,
> Hrishikesh
> 
> On Mon, Nov 8, 2021 at 8:19 PM Hrishikesh Karanjikar 
> mailto: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 executable, UCB RISC-V, version 1 (SYSV), dynamically 
> linked, interpreter /lib/ld-linux-riscv64-lp64d.so.1, 
> BuildID[sha1]=51ac741e44727379a0fbb5936acea4d7b8bdd624, for GNU/Linux 4.15.0, 
> with debug_info, not stripped
> 
> And run with qemu:
> 
> $ qemu-riscv64-static ./bin/vpp unix interactive
> buffer  [warn  ]: numa[0] falling back to non-hugepage backed buffer pool 
> (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to mmap 19 pages 
> at 0x404fc0 fd 4 numa 0 flags 0x11: Invalid argument)
> buffer  [warn  ]: numa[1] falling back to non-hugepage backed buffer pool 
> (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set mempolicy 
> for numa node 1: Function not implemented)
> vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set mempolicy 
> for numa node 1: Function not implementedsvm_queue_init:57: mutex_init: No 
> such file or directory (errno 2)
> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
> vat-plug/load  [error ]: vat_plugin_register: oddbuf plugin not loaded...
> _____   _  ___
>  __/ __/ _ \  (_)__| | / / _ \/ _ \
>  _/ _// // / / / _ \   | |/ / ___/ ___/
>  /_/ /(_)_/\___/   |___/_/  /_/
> 
> DBGvpp#
> 
> 
> — 
> Damjan
> 
> 
> 
> > On 08.11.2021., at 14:59, Hrishikesh Karanjikar 
> > mailto:hrishikesh.karanji...@gmail.com>> 
> > wrote:
> > 
> > Hi,
> > 
> > Thanks for this patch. I will check it out. Which compile did you use? Did 
> > you cross compile or locally compiled it on Qemu or any other platform?
> > I was able to compile VPP using GCC10 locally on Qemu but I had to do other 
> > modifications.
> > At many places I was able to put RiscV specific code but vector support for 
> > RiscV is still not available so I had to use stubs for compilation to work.
> > 
> > Thanks,
> > Hrishikesh
> > 
> > On Mon, Nov 1, 2021 at 1:53 AM Damjan Marion  > > wrote:
> > 
> > Here it is:
> > 
> > 

Re: [vpp-dev] About Risc-V Porting

[Hrishikesh Karanjikar]

Hi,

One more thing.
Did you compile with DPDK?
I compiled with DPDK. I have ported DPDK for Risc-V. Not upstreamed yet.
I had to compile without rdma-core.



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 executable, UCB RISC-V, version 1 (SYSV),
>> dynamically linked, interpreter /lib/ld-linux-riscv64-lp64d.so.1,
>> BuildID[sha1]=51ac741e44727379a0fbb5936acea4d7b8bdd624, for GNU/Linux
>> 4.15.0, with debug_info, not stripped
>>
>> And run with qemu:
>>
>> $ qemu-riscv64-static ./bin/vpp unix interactive
>> buffer  [warn  ]: numa[0] falling back to non-hugepage backed buffer
>> pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to mmap 19
>> pages at 0x404fc0 fd 4 numa 0 flags 0x11: Invalid argument)
>> buffer  [warn  ]: numa[1] falling back to non-hugepage backed buffer
>> pool (vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set
>> mempolicy for numa node 1: Function not implemented)
>> vlib_physmem_shared_map_create: pmalloc_map_pages: failed to set
>> mempolicy for numa node 1: Function not implementedsvm_queue_init:57:
>> mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> svm_queue_init:57: mutex_init: No such file or directory (errno 2)
>> vat-plug/load  [error ]: vat_plugin_register: oddbuf plugin not
>> loaded...
>> _____   _  ___
>>  __/ __/ _ \  (_)__| | / / _ \/ _ \
>>  _/ _// // / / / _ \   | |/ / ___/ ___/
>>  /_/ /(_)_/\___/   |___/_/  /_/
>>
>> DBGvpp#
>>
>>
>> —
>> Damjan
>>
>>
>>
>> > On 08.11.2021., at 14:59, Hrishikesh Karanjikar <
>> hrishikesh.karanji...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > Thanks for this patch. I will check it out. Which compile did you use?
>> Did you cross compile or locally compiled it on Qemu or any other platform?
>> > I was able to compile VPP using GCC10 locally on Qemu but I had to do
>> other modifications.
>> > At many places I was able to put RiscV specific code but vector support
>> for RiscV is still not available so I had to use stubs for compilation to
>> work.
>> >
>> > Thanks,
>> > Hrishikesh
>> >
>> > On Mon, Nov 1, 2021 at 1:53 AM Damjan Marion  wrote:
>> >
>> > Here it is:
>> >
>> > https://gerrit.fd.io/r/c/vpp/+/34298
>> >
>> > It is early but works for me.
>> >
>> > —
>> > Damjan
>> >
>> >
>> >> On 25.10.2021., at 18:36, Hrishikesh Karanjikar <
>> hrishikesh.karanji...@gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> Yes. SiFive HiFive boards are available. But they do not support
>> Vector Extension 

Re: [vpp-dev] About Risc-V Porting

[Hrishikesh Karanjikar]

Hi,

Thanks for this patch. I will check it out. Which compile did you use? Did
you cross compile or locally compiled it on Qemu or any other platform?
I was able to compile VPP using GCC10 locally on Qemu but I had to do other
modifications.
At many places I was able to put RiscV specific code but vector support for
RiscV is still not available so I had to use stubs for compilation to work.

Thanks,
Hrishikesh

On Mon, Nov 1, 2021 at 1:53 AM Damjan Marion  wrote:

>
> Here it is:
>
> https://gerrit.fd.io/r/c/vpp/+/34298
>
> It is early but works for me.
>
> —
> Damjan
>
>
> On 25.10.2021., at 18:36, Hrishikesh Karanjikar <
> hrishikesh.karanji...@gmail.com> wrote:
>
> Hi,
>
> Yes. SiFive HiFive boards are available. But they do not support Vector
> Extension yet.
> Also Qemu is ready for RiscV. Ubuntu images are available for RIscV.
>
> Thanks,
> Hrishikesh
>
>
> On Mon, Oct 25, 2021 at 9:56 PM Damjan Marion  wrote:
>
>>
>>
>>
>> > On 14.10.2021., at 15:43, Hrishikesh Karanjikar <
>> hrishikesh.karanji...@gmail.com> wrote:
>> >
>> >
>> > Hi,
>> >
>> > Is VPP ported for the Risc-V processor?
>> > Is there any project going for the same?
>> >
>>
>> I was looking at that a year ago but I was not able to find any suitable
>> dev board.
>>
>> Is there anything new on the market?
>>
>> —
>> Damjan
>>
>>
>
> --
>
> Regards,
> Hrishikesh Karanjikar
>
> 
>
>
>

-- 

Regards,
Hrishikesh Karanjikar

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20447): https://lists.fd.io/g/vpp-dev/message/20447
Mute This Topic: https://lists.fd.io/mt/86312689/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] About Risc-V Porting

[Damjan Marion via lists.fd.io]

Here it is:

https://gerrit.fd.io/r/c/vpp/+/34298 

It is early but works for me.

— 
Damjan


> On 25.10.2021., at 18:36, Hrishikesh Karanjikar 
>  wrote:
> 
> Hi,
> 
> Yes. SiFive HiFive boards are available. But they do not support Vector 
> Extension yet.
> Also Qemu is ready for RiscV. Ubuntu images are available for RIscV.
> 
> Thanks,
> Hrishikesh
> 
> 
> On Mon, Oct 25, 2021 at 9:56 PM Damjan Marion  > wrote:
> 
> 
> 
> > On 14.10.2021., at 15:43, Hrishikesh Karanjikar 
> > mailto:hrishikesh.karanji...@gmail.com>> 
> > wrote:
> > 
> > 
> > Hi,
> > 
> > Is VPP ported for the Risc-V processor?
> > Is there any project going for the same?
> > 
> 
> I was looking at that a year ago but I was not able to find any suitable dev 
> board.
> 
> Is there anything new on the market?
> 
> — 
> Damjan
> 
> 
> 
> -- 
> 
> Regards,
> Hrishikesh Karanjikar
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20400): https://lists.fd.io/g/vpp-dev/message/20400
Mute This Topic: https://lists.fd.io/mt/86312689/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] About Risc-V Porting

[Hrishikesh Karanjikar]

Hi,

Yes. SiFive HiFive boards are available. But they do not support Vector
Extension yet.
Also Qemu is ready for RiscV. Ubuntu images are available for RIscV.

Thanks,
Hrishikesh


On Mon, Oct 25, 2021 at 9:56 PM Damjan Marion  wrote:

>
>
>
> > On 14.10.2021., at 15:43, Hrishikesh Karanjikar <
> hrishikesh.karanji...@gmail.com> wrote:
> >
> >
> > Hi,
> >
> > Is VPP ported for the Risc-V processor?
> > Is there any project going for the same?
> >
>
> I was looking at that a year ago but I was not able to find any suitable
> dev board.
>
> Is there anything new on the market?
>
> —
> Damjan
>
>

-- 

Regards,
Hrishikesh Karanjikar

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20384): https://lists.fd.io/g/vpp-dev/message/20384
Mute This Topic: https://lists.fd.io/mt/86312689/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] About Risc-V Porting

[Damjan Marion via lists.fd.io]

> On 14.10.2021., at 15:43, Hrishikesh Karanjikar 
>  wrote:
> 
> 
> Hi,
> 
> Is VPP ported for the Risc-V processor?
> Is there any project going for the same?
> 

I was looking at that a year ago but I was not able to find any suitable dev 
board.

Is there anything new on the market?

— 
Damjan


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20383): https://lists.fd.io/g/vpp-dev/message/20383
Mute This Topic: https://lists.fd.io/mt/86312689/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] About Risc-V Porting

[Hrishikesh Karanjikar]

Hi,

Is VPP ported for the Risc-V processor?
Is there any project going for the same?

-- 

Regards,
Hrishikesh Karanjikar

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20333): https://lists.fd.io/g/vpp-dev/message/20333
Mute This Topic: https://lists.fd.io/mt/86312689/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-