From: Nishant Verma <vnish11@gmail.com>
To: Saint Michael <venefax@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Compiling fails
Date: Thu, 21 May 2020 23:24:11 -0400 [thread overview]
Message-ID: <CAHhCjUHFpEWVcF96HST2QtcDmxtHZxG7FODXhk2iJdVFq5koFg@mail.gmail.com> (raw)
In-Reply-To: <CAHhCjUHf0i3UHQqUJ6F2NTxhr5WDjw6y3pQFmb8BvyfEetuXDg@mail.gmail.com>
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 <vnish11@gmail.com> 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 <venefax@gmail.com> 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
prev parent reply other threads:[~2020-05-22 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 15:43 Saint Michael
2020-05-22 3:21 ` Nishant Verma
2020-05-22 3:24 ` Nishant Verma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHhCjUHFpEWVcF96HST2QtcDmxtHZxG7FODXhk2iJdVFq5koFg@mail.gmail.com \
--to=vnish11@gmail.com \
--cc=users@dpdk.org \
--cc=venefax@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).