DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Tapio Tallgren <tapio.tallgren@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Newbie question: compiling virtio-net-pmd v1.2 fails with dpdk 1.7 on a VM
Date: Thu, 20 Nov 2014 06:17:27 -0500	[thread overview]
Message-ID: <20141120111727.GA2609@hmsreliant.think-freely.org> (raw)
In-Reply-To: <CAJi57Qn8MbCNMS9K3TaBEKMUT6CXfDtkqXiy2sNajejNXBj4WQ@mail.gmail.com>

On Thu, Nov 20, 2014 at 09:14:35AM +0200, Tapio Tallgren wrote:
> Hi,
> 
> I am probably doing something obviously wrong but I cannot figure it out
> right now..
> I have dpdk version 1.7.1 installed and compiled (from the git repository)
> and virtio-net-pmd driver version v1.2 from git.dpdk.org. When I try to
> compile virtio-net-pmd with
> 
> make RTE_INCLUDE=../dpdk/build/include
> 
> I get errors like this:
> 
> virtio_user.c: In function rte_rmxbuf_alloc:
> virtio_user.c:208:44: error: macro "__rte_mbuf_sanity_check" passed 3
> arguments, but takes just 2
> 
> Looks like a version conflict? Dpdk 1.7 should support virtio-pmd so what
> am I doing wrong?
> 
> -- 
> -Tapio
> 

Nothing, its a bug.  DPDK changed the API here with commit
9aaccf1abdb2894ec23870e1d2199a657f85850e but it never got changed in the
virtio_user pmd.  You need to modify the pmd like the other call sites have been
in the above commit.

This is why those external pmds need to be merged into the dpdk tree.

Neil

  reply	other threads:[~2014-11-20 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  7:14 Tapio Tallgren
2014-11-20 11:17 ` Neil Horman [this message]
2014-11-20 11:33   ` Thomas Monjalon
2014-11-20 12:37     ` Tapio Tallgren
2014-11-20 14:17       ` Neil Horman

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=20141120111727.GA2609@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=tapio.tallgren@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).