DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: "DE LARA GUARCH, PABLO" <pablo.de.lara.guarch@intel.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Build failure on Ubuntu 14.04
Date: Mon, 7 Jul 2014 15:24:28 +0000	[thread overview]
Message-ID: <DE059B67-924E-4C1F-B010-E17E04407BAA@windriver.com> (raw)
In-Reply-To: <51574BBB-97CF-492E-97D0-52207F884BE5@windriver.com>


BTW, he changed the value from 100 to 400 and that fixed his compile problem on CentOS.

Keith Wiles, Principal Technologist with CTO office, Wind River
mobile 972-213-5533

[Powering 30 Years of Innovation]<http://www.windriver.com/announces/wr30/>

On Jul 7, 2014, at 9:59 AM, Wiles, Roger Keith <keith.wiles@windriver.com<mailto:keith.wiles@windriver.com>> wrote:

The guy using CentOS stated if he changed the code to compare with KERNEL_VERSION(3,13,8) it works.

Also the compiler is older on CentOS gcc 4.4.7 and has a problem with the:
"--param max-inline-insns-single=100" issue in librte_eal/linuxapp/igb_uio/Makefile

Giving the error:
"error: inlining failed in call to 'kzalloc.clone.0': --param max-inline-insns-single limit reached" when compiling igb_uio.o

He suggested increasing the value to 1000, but he got that suggestion from stack overflow site.

I do not use CentOS and can not verify the issues or fix.

Thanks
++Keith

Keith Wiles, Principal Technologist with CTO office, Wind River
mobile 972-213-5533

[Powering 30 Years of Innovation]<http://www.windriver.com/announces/wr30/>

On Jul 7, 2014, at 9:41 AM, Wiles, Roger Keith <keith.wiles@windriver.com<mailto:keith.wiles@windriver.com><mailto:keith.wiles@windriver.com>> wrote:

Someone compiling on CentOS kernel 3.13.7 needed the original code. Looks like some other type of ifdef change needs to be done to the kcompat.h file to allow it to compile on Ubuntu 14.04 with kernel 3.13.0-30.

Keith Wiles, Principal Technologist with CTO office, Wind River
mobile 972-213-5533

[Powering 30 Years of Innovation]<http://www.windriver.com/announces/wr30/>

On Jul 7, 2014, at 3:39 AM, De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com<mailto:pablo.de.lara.guarch@intel.com><mailto:pablo.de.lara.guarch@intel.com><mailto:pablo.de.lara.guarch@intel.com>> wrote:


Hi Keith,

we built the newest dpdk code on my machine, it seems OK,
please see UB14.04 info in my computer.
System:       Ubuntu14.04
Kernel:       3.13.0-24 X86_64
Compiler:     GCC 4.8.2 x86_64

Can you let me know which kernel version you use?

Apparently, it is this one: 3.13.0-30-generic, from uname -a

Thanks
Waterman

  reply	other threads:[~2014-07-07 15:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 15:27 Wiles, Roger Keith
2014-07-05 15:28 ` Wiles, Roger Keith
2014-07-05 15:50   ` Wiles, Roger Keith
2014-07-07  8:13     ` Cao, Waterman
2014-07-07  8:39       ` De Lara Guarch, Pablo
2014-07-07 14:41         ` Wiles, Roger Keith
2014-07-07 14:59           ` Wiles, Roger Keith
2014-07-07 15:24             ` Wiles, Roger Keith [this message]
2014-07-16 16:48               ` Murugesan, AnbarasanX
2014-07-08  2:12           ` Cao, Waterman
2014-07-08 14:35             ` Wiles, Roger Keith
2014-07-11  8:00       ` Choi, Sy Jong
2014-07-11  8:43 ` Masaru Oki

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=DE059B67-924E-4C1F-B010-E17E04407BAA@windriver.com \
    --to=keith.wiles@windriver.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.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).