DPDK usage discussions
 help / color / mirror / Atom feed
From: David Aldrich <david.aldrich.ntml@gmail.com>
To: Vincent Li <vincent.mc.li@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] How to install DPDK kernel module?
Date: Thu, 4 Jun 2020 17:42:59 +0100	[thread overview]
Message-ID: <CAJK_iej2S+BfXAJsCCHmJhuGGZnrU4GHUVqiF-_0xsKTGXdQZw@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.21.2006040812560.15000@sea-ml-00029224.olympus.f5net.com>

>
> On Thu, 4 Jun 2020, David Aldrich wrote:
>
> > I have installed dpdk 18.08 on a Centos 7 machine, which has the kernel
> > source installed.
> >
> > I built dpdk using:
> >
> > $ make -j T=x86_64-native-linuxapp-gcc install
> > <snip>
> > Build complete [x86_64-native-linuxapp-gcc]
> > Installation cannot run with T defined and DESTDIR undefined
> >
> > I want to interface dpdk to a HP NIC that uses the Intel X722 chipset.
> So I
> > then run:
> >
> > $ /opt/dpdk/dpdk-18.08/usertools/dpdk-devbind.py -b igb_uio `lspci |
> > grep X722 | awk '{print $1}'`
> > Error - no supported modules(DPDK driver) are loaded
>
> probably igb_uio kernel module is not loaded, run lsmod to check if
> igb_uio is loaded
>
> >
> > I think that this error means that the DPDK kernel module is not
> installed.
> >
> > How can I fix this?
> >
>
> I usually use dpdk-setup.sh script from the dpdk source to compile and
> load igb_uio, and bind the NIC to igb_uio. otherwise, you may need to
> setup proper environment varibles to find and load the igb_uio module
> properly, I think distribution like Centos or Ubuntu has the proper DPDK
> script to load and bind NIC to DPDK drivers.
>

Thanks for your answer. Identifying the igb_uio module as necessary really
helped me. Module is loaded now.

On Thu, Jun 4, 2020 at 4:17 PM Vincent Li <vincent.mc.li@gmail.com> wrote:

>
>
>
>
> On Thu, 4 Jun 2020, David Aldrich wrote:
>
> > I have installed dpdk 18.08 on a Centos 7 machine, which has the kernel
> > source installed.
> >
> > I built dpdk using:
> >
> > $ make -j T=x86_64-native-linuxapp-gcc install
> > <snip>
> > Build complete [x86_64-native-linuxapp-gcc]
> > Installation cannot run with T defined and DESTDIR undefined
> >
> > I want to interface dpdk to a HP NIC that uses the Intel X722 chipset.
> So I
> > then run:
> >
> > $ /opt/dpdk/dpdk-18.08/usertools/dpdk-devbind.py -b igb_uio `lspci |
> > grep X722 | awk '{print $1}'`
> > Error - no supported modules(DPDK driver) are loaded
>
> probably igb_uio kernel module is not loaded, run lsmod to check if
> igb_uio is loaded
>
> >
> > I think that this error means that the DPDK kernel module is not
> installed.
> >
> > How can I fix this?
> >
>
> I usually use dpdk-setup.sh script from the dpdk source to compile and
> load igb_uio, and bind the NIC to igb_uio. otherwise, you may need to
> setup proper environment varibles to find and load the igb_uio module
> properly, I think distribution like Centos or Ubuntu has the proper DPDK
> script to load and bind NIC to DPDK drivers.
>

      reply	other threads:[~2020-06-04 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 14:33 David Aldrich
2020-06-04 15:17 ` Vincent Li
2020-06-04 16:42   ` David Aldrich [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=CAJK_iej2S+BfXAJsCCHmJhuGGZnrU4GHUVqiF-_0xsKTGXdQZw@mail.gmail.com \
    --to=david.aldrich.ntml@gmail.com \
    --cc=users@dpdk.org \
    --cc=vincent.mc.li@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).