DPDK usage discussions
 help / color / mirror / Atom feed
From: Murali Krishna <murali.krishna@broadcom.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] dpdk 2.2.0 build failure on Rhel 6.8 Beta 1 Kernel
Date: Wed, 23 Mar 2016 20:30:07 +0530	[thread overview]
Message-ID: <ad1955673a2bd359bb3a1bc0d5b9ff4e@mail.gmail.com> (raw)
In-Reply-To: <9791503.gmfYu7J9gH@xps13>

After disabling KNI(CONFIG_RTE_KNI_KMOD=n), dpdk 2.2.0 got compiled
successfully on Rhel 6.8 Kernel(2.6.32-621.el6.x86_64).

Thanks,
Murali


-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Wednesday, March 23, 2016 8:20 PM
To: Murali Krishna
Cc: users@dpdk.org
Subject: Re: [dpdk-users] dpdk 2.2.0 build failure on Rhel 6.8 Beta 1 Kernel

2016-03-23 20:08, Murali Krishna:
> Hi Thomas,
>
> I tried workaround 1, 2 and 3.
>
> 1. I still see some errors after disabling igb_uio(setting
> CONFIG_RTE_EAL_IGB_UIO=n in x86_64-native-linuxapp-gcc/.config) in the
> same kernel(2.6.32-621.el6.x86_64). Please see the attachment for
> detailed error information.

You must disable KNI which is also failing:
	CONFIG_RTE_KNI_KMOD=n

> 2. I tried to build dpdk 2.2.0 on Rhel7.2
> kernel(3.10.0-327.el7.x86_64) and I didn’t see any errors.
>
> 3. I tried to compile older DPDKs(DPDK 1.7.1, DPDK 1.8.0 and DPDK
> 2.0.0) on the same Rhel6.8 kernel(2.6.32-621.el6.x86_64). I am seeing
> the same errors which I observed while building dpdk 2.2.0 when I try
> to compile older DPDKs(DPDK 1.7.1, DPDK 1.8.0 and DPDK 2.0.0)

It is hard to maintain these out of tree modules for kernels receiving a lot
of backports.

> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> 2016-03-23 19:04, Murali Krishna:
> > [root@Rhel68B1 dpdk-2.2.0]# cat /etc/redhat-release
> >
> > Red Hat Enterprise Linux Server release 6.8 Beta (Santiago)
> >
> > [root@Rhel68B1 dpdk-2.2.0]# uname -a
> >
> > Linux Rhel68B1 2.6.32-621.el6.x86_64 #1 SMP Wed Feb 24 00:07:06 EST
> > 2016
> > x86_64 x86_64 x86_64 GNU/Linux
> [...]
> > /root/dpdk-2.2.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:213:
> > error: ‘PCI_MSIX_ENTRY_CTRL_MASKBIT’ undeclared (first use in this
> > function)
> [...]
> > Is there any workaround for this?
>
> Yes there are a lot of workarounds (see the 4 proposals below).
> igb_uio is an out-of-tree kernel module.
> We are replacing it with upstream modules uio_pci_generic or vfio.
>
> 1/ Try to disable igb_uio in your config
> (x86_64-native-linuxapp-gcc/.config):
> 	CONFIG_RTE_EAL_IGB_UIO=n
> 2/ If you want igb_uio, you should upgrade your kernel 3/ If you want
> to keep this kernel, you can try an older DPDK version 4/ If you want
> to keep this kernel and this DPDK, you can try to fix
> 	the issue and submit a patch to dev@dpdk.org.

  reply	other threads:[~2016-03-23 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 13:34 Murali Krishna
2016-03-23 14:00 ` Thomas Monjalon
2016-03-23 14:38   ` Murali Krishna
2016-03-23 14:49     ` Thomas Monjalon
2016-03-23 15:00       ` Murali Krishna [this message]
2016-03-23 14:52   ` Murali Krishna
2016-03-23 15:05   ` Murali Krishna

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=ad1955673a2bd359bb3a1bc0d5b9ff4e@mail.gmail.com \
    --to=murali.krishna@broadcom.com \
    --cc=thomas.monjalon@6wind.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).