From: sothy shan <sothy.e98@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
Date: Thu, 25 Dec 2014 10:11:51 +0100 [thread overview]
Message-ID: <CAHcF_0bCX8qc3xTJGw8kM3B8AzQpgxGghqs+ctYyRycgKsvEUQ@mail.gmail.com> (raw)
In-Reply-To: <20141224150401.GB23653@localhost.localdomain>
On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <nhorman@tuxdriver.com> wrote:
> On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > Hello!
> >
> > I am playing with DPDK 1.7.1 in Fedora.
> >
> > When I do like this:
> >
> > export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > make install T="$RTE_TARGET"
> >
> > It worked. Means Testpmd is running.
> >
> > When I run as mentioned below:
> >
> > make CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET"
> >
> > Build is sucess. But Testpmd gives error.
> >
> > Error is :
> >
> The dpdk ivshmem build assumes the presence of ivshmem devices as plumbed
> by
> qemu virtual guests. If you don't have a qemu guest running dpdk won't
> find any
> shared memory devices, which is exactly what you are seeing. That said,
> even if
> you are running qemu guests, IIRC Fedora doesn't enable ivshmem because
> the code
> has some security and behavioral issues still I think. You'll need to
> rebuild
> qemu to add support for it.
>
My understanding is that It is problem of enabling
CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build target of
x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect an
error because of shared lib flag.
Sothy
>
> Neil
>
>
next prev parent reply other threads:[~2014-12-25 9:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 13:26 sothy shan
2014-12-24 15:03 ` Masaru Oki
2014-12-24 15:04 ` Neil Horman
2014-12-25 9:11 ` sothy shan [this message]
2014-12-25 17:08 ` Neil Horman
2014-12-26 8:01 ` sothy shan
2014-12-26 14:37 ` Neil Horman
2015-01-09 16:20 ` sothy shan
2015-01-10 12:44 ` Neil Horman
2015-01-16 14:10 ` sothy shan
2015-01-16 14:27 ` Olivier MATZ
2015-01-16 16:07 ` sothy shan
2015-01-16 16:35 ` Olivier MATZ
2015-01-16 16:47 ` sothy shan
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=CAHcF_0bCX8qc3xTJGw8kM3B8AzQpgxGghqs+ctYyRycgKsvEUQ@mail.gmail.com \
--to=sothy.e98@gmail.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.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).