Adding answer for your second question. for ko for rte_kni, first you need to compile then you will be able to get that.
I suggest you to use dpdk-setup.sh present in usertools folder. On Thu, May 21, 2020 at 11:21 PM Nishant Verma <[email protected]> wrote: > Please check the sec 3 of GSG. > Actually, what dpdk make procedure is looking for, DESTDIR for it to store > the lib and other stuff. > > make install T=$RTE_TARGET DESTDIR=$DESTINATION_DIR > > Here, RTE_TARGET is your target for example x86_64-native-linux-gcc > & > DESTINATION_DIR is any folder location where you want to store the libs. > > > On Sun, May 10, 2020 at 11:43 AM Saint Michael <[email protected]> wrote: > >> I downloaded dpdk-20.02.tar.xz and run source usertools/dpdk-setup.sh but >> the script fails to install with "Installation cannot run with T defined >> and DESTDIR undefined" >> >> I also need to build rtr_kni.ko, for my kernel 5.6.12-1.el7.elrepo.x86_64, >> but the module that I need to compile, "rte_kni.ko" is not available, all >> I >> see is >> find -name "rte_kni*" >> ./lib/librte_kni/rte_kni.h >> ./lib/librte_kni/rte_kni_version.map >> ./lib/librte_kni/rte_kni.c >> ./lib/librte_kni/rte_kni_fifo.h >> ./lib/librte_eal/linux/eal/include/rte_kni_common.h >> ./x86_64-native-linux-gcc/build/lib/librte_kni/rte_kni.o >> ./x86_64-native-linux-gcc/include/rte_kni.h >> ./x86_64-native-linux-gcc/include/rte_kni_common.h >> >> kindly help me understand what am I doing wrong? My goal is to pin two >> network interfaces to a single core each, to accelerate packet processing. >> Philip >> > > > -- > Rgds, > Nishant > > > > -- Rgds, Nishant
