DPDK usage discussions
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
To: "Trahe, Fiona" <fiona.trahe@intel.com>
Cc: 宋捷 <songj@zctt.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] 答?: igb_uio.ko is not generated via make/dpdk-setup.sh
Date: Mon, 20 Apr 2020 19:02:50 +0900	[thread overview]
Message-ID: <20200420190249.54A5.17218CA3@ntt-tx.co.jp_1> (raw)
In-Reply-To: <SN6PR11MB2880CE7F54A7DD85D9861318E4D90@SN6PR11MB2880.namprd11.prod.outlook.com>

Hello Fiona,

Thanks for your response.
In short,
you are absolutely correct! Thanks!

When I changed the config and re-compile DPDK, IGB_UIO genereated.
However no documents about this default behavior change.

In my opinion, it may be "kind" if such change is clearly documented.

BR,
Hideyuki Yamashita
NTT TechnoCross

> Hi 
> 
> Have you tried setting CONFIG_RTE_EAL_IGB_UIO=y in the config file.
> The default has changed from y to n in some recent release.
> as it is more advisable to use vfio-pci instead.
> 
> Fiona
> 
> > -----Original Message-----
> > From: users <users-bounces@dpdk.org> On Behalf Of Hideyuki Yamashita
> > Sent: Friday, April 17, 2020 9:02 AM
> > To: 宋捷 <songj@zctt.com>
> > Cc: users@dpdk.org
> > Subject: Re: [dpdk-users] 答?: igb_uio.ko is not generated via make/dpdk-setup.sh
> > 
> > Hello Songi,
> > 
> > Thanks for your checking the issue.
> > 
> > I think that considering that two person encountered the same issue,
> > it looks that it is not coincident.
> > It is highly possible that there is some problem with building "make"
> > system.
> > 
> > If I deeply look into make file, I can fix my problem.
> > But I am not good at looking/analyzing make file.
> > 
> > So DPDK experts,
> > I need, we need some explanation or fix for this isssue!
> > 
> > Thanks for your help.
> > 
> > BR,
> > Hideyuki Yamashita
> > NTT TechnoCross
> > 
> > > I get the same issue」ャ
> > > I build DPDK 20.02 with "make install T=x86_64-native-linuxapp-gcc", there
> > > is not kmod folder under x86_64-native-linuxapp-gcc.
> > > So I have to copy kmod from dpdk-stable-19.11.1 into DPDK 20.02, the igb_uio
> > > source code is same between these two version.
> > >
> > >
> > >
> > >
> > > -----モハシ?ヤュシ?-----
> > > キ「シ?ネヒ: users [mailto:users-bounces@dpdk.org] エ〓・Hideyuki Yamashita
> > > キ「ヒヘハアシ Friday, April 17, 2020 2:18 PM
> > > ハユシ?ネヒ: users@dpdk.org; Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
> > > ヨ〓 Re: [dpdk-users] igb_uio.ko is not generated via make/dpdk-setup.sh
> > >
> > > Hello Experts,
> > >
> > > Can anybody help me out?
> > >
> > > BR,
> > > Hideyuki Yamashita
> > > NTT TechnoCross
> > >
> > > > Hello,
> > > >
> > > > I have problem with dpdk-20.02 when compiling.
> > > >
> > > > [1. What is the problem]
> > > > igb_uio.ko is not generated under build/kmod/ directory thus I can not
> > > > load/bind NIC with igb_uio.
> > > >
> > > > [2.Which platform]
> > > > x86_64
> > > > Ubuntu 18.04.04 LTS
> > > >
> > > > [3.Which build target]
> > > > x86_64-native-linux-gcc
> > > > x86_64-native-linuxapp-gcc
> > > >
> > > > I used dpdk-20.02 tarball which can be downloaded via website.
> > > >
> > > > [4.How I compiled source]
> > > > I tried the follwoing two ways but both failed to generate igb_uio
> > > > module.
> > > >
> > > > 4a
> > > > #sudo make install T=x86_64-native-linuxapp-gcc #sudo make install
> > > > T=x86_64-native-linux-gcc
> > > >
> > > > 4b
> > > > [for 19.11]
> > > > [38] x86_64-native-linuxapp-gcc
> > > > [45] Insert IGB UIO module
> > > > [50] Display current Ethernet/Baseband/Crypto device settings
> > > >
> > > > All successful
> > > >
> > > > [for 20.02]
> > > > [41] x86_64-native-linux-gcc
> > > > [45] Insert IGB UIO module
> > > >
> > > > Option: 45
> > > >
> > > > ## ERROR: Target does not have the DPDK UIO Kernel Module.
> > > >        To fix, please try to rebuild target.
> > > >
> > > > [for 20.02]
> > > > [38] x86_64-native-linuxapp-gcc
> > > > [45] Insert IGB UIO module
> > > >
> > > > Option: 45
> > > >
> > > > ## ERROR: Target does not have the DPDK UIO Kernel Module.
> > > >        To fix, please try to rebuild target.
> > > >
> > > > With regard to 19.11, using usertools/dpdk-setup.sh perfectly worked.
> > > > However something looks wrong with 20.02.
> > > > I've heard that building system is moving from "make"
> > > > to "meason". But following the official document "make" is still
> > > > supported. So for me it is very odd.
> > > >
> > > >
> > > > Thanks in advance!
> > > >
> > > > BR,
> > > > Hideyuki Yamashita
> > > > NTT TechnoCross
> > >
> > >
> > >
> > >
> > 



  reply	other threads:[~2020-04-20 10:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  6:36 [dpdk-users] " Hideyuki Yamashita
2020-04-17  6:17 ` Hideyuki Yamashita
2020-04-17  7:51   ` [dpdk-users] 答复: " 宋捷
     [not found]   ` <0D293C5FA1DB70FF@nttdocomo.co.jp>
2020-04-17  8:02     ` [dpdk-users] 答?: " Hideyuki Yamashita
2020-04-17  8:59       ` Trahe, Fiona
2020-04-20 10:02         ` Hideyuki Yamashita [this message]
2020-04-20 12:23           ` Trahe, Fiona

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=20200420190249.54A5.17218CA3@ntt-tx.co.jp_1 \
    --to=yamashita.hideyuki@ntt-tx.co.jp \
    --cc=fiona.trahe@intel.com \
    --cc=songj@zctt.com \
    --cc=users@dpdk.org \
    /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).