DPDK usage discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Royce Niu <royceniu@gmail.com>, users@dpdk.org
Subject: Re: [dpdk-users] Fail to build Memnic in Ubuntu 14.04
Date: Tue, 19 Jan 2016 22:49:36 -0800	[thread overview]
Message-ID: <569F2E00.2090400@mhcomputing.net> (raw)
In-Reply-To: <CAOwUCNsnVys1rr3PcjggsrBwz90Bufjb26Hi15p0cROOn8C3oA@mail.gmail.com>

On 1/19/16 10:03 PM, Royce Niu wrote:
> Hi
>
> I want to install an OVS/memnic software in a KVM virtual machine.
>
> For the higher speed, I install memnic/pmd (SR-IOV) instead of virtio,
> since I believe SR-IOV is faster than virtio.
>
> But, I meet some trouble when I build the memnic following the doc (
> http://dpdk.org/doc/memnic-pmd)
>
> I download the most updated software DPDK 2.2.0 and memnic 1.3.
>
> My system is :
> 1. 2 VCPU 2G Mem
> 2. Ubuntu 14.04 64bit
> 3. Updated packages
>
>
> I build DPDK successfully, but when I build memnic in VM according to the
> doc.

Hello,

The memnic code is not updated since 2014-09-30. I am not sure if it got 
replaced by something else in OVS or just fell asleep.

But I think that is why you are getting so insanely many errors, it fell 
too far behind DPDK to work.

If you can find an old DPDK released around this time listed here it 
might help narrow down if that might be the root cause:

http://dpdk.org/browse/memnic/log/

However a DPDK that old will probably fail to build due to kernel 
version issues.

Matthew.

  reply	other threads:[~2016-01-20  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20  6:03 Royce Niu
2016-01-20  6:49 ` Matthew Hall [this message]
2016-01-20 15:27   ` Royce Niu

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=569F2E00.2090400@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=royceniu@gmail.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).