DPDK patches and discussions
 help / color / mirror / Atom feed
From: BYEONG-GI KIM <kimbyeonggi@gmail.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	altoarun@gmail.com, Dpdk-ovs@lists.01.org, dev@dpdk.org
Subject: Re: [dpdk-dev] No "pci_unbind.py" in tools subdirectory
Date: Mon, 14 Jul 2014 17:29:14 +0900	[thread overview]
Message-ID: <CAEHt_JbqByL11VQqTxNmAUKQRZiiGzOs2GP=5Qx+k_MT6JJjwg@mail.gmail.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D89721C31B0D@IRSMSX103.ger.corp.intel.com>

Thank you for the reply.

By the way, I got an error message while compiling Open vSwitch. Is it
essential to bind a port to igb_uio module in order to compile Open vSwitch
without error? I just wonder whether the errors attached below just
happened because I did not bind the port to the module or not...

make RTE_TARGET=x86_64-ivshmem-linuxapp-gcc
...
/home/stack/dpdk/dpdk-1.6.0r2/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal.o):
In function `rte_eal_init':
eal.c:(.text+0xedf): undefined reference to `dlopen'
eal.c:(.text+0xefe): undefined reference to `dlerror'
collect2: error: ld returned 1 exit status
make[2]: *** [utilities/ovs-controller] Error 1
make[2]: Leaving directory `/home/stack/dpdk-ovs/openvswitch'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stack/dpdk-ovs/openvswitch'
make: *** [all] Error 2

Best regards

Byeong-Gi KIM


2014-07-14 17:10 GMT+09:00 De Lara Guarch, Pablo <
pablo.de.lara.guarch@intel.com>:

> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Aravind
> > Sent: Monday, July 14, 2014 8:52 AM
> > To: BYEONG-GI KIM
> > Cc: dev@dpdk.org; Dpdk-ovs@lists.01.org
> > Subject: Re: [dpdk-dev] No "pci_unbind.py" in tools subdirectory
> >
> > Hi,
> >
> > You should be using igb_uio_bind.py , have a look at the quick start
> guide
> > : http://dpdk.org/doc/quick-start
> >
>
> Actually, now it is called dpdk_nic_bind.py :)
>
> >
> >
> > On Mon, Jul 14, 2014 at 1:09 PM, BYEONG-GI KIM <kimbyeonggi@gmail.com>
> > wrote:
> >
> > > Hello.
> > >
> > > I'm sorry for the repeated question.
> > >
> > > I finally compiled DPDK successfully (there was a problem in the source
> > > code what I downloaded), and I'm moving to compile dpdk-ovs.
> > >
> > > Before compiling it, I'm trying to binding a network port to igb_uio
> > > module. In the dpdk-getting-started-guide, "pci_unbind.py" utility
> script
> > > is used to provide a view of the current state of the network ports on
> the
> > > system, and to bind/unbind those ports from the different kernel
> modules.
> > >
> > > The script, however, was not there in tools directory; There were only
> > > "igb_uio_bind.py". Is it fine as it is, or do I miss something?
> > >
> > > I downloaded the DPDK source from http://dpdk.org/browse/dpdk/refs/,
> and
> > > the file was dpdk-1.6.0r2.zip. I compiled both
> x86-64-defaultlinuxapp-gcc
> > > and x86-64-ivshmem-linuxapp-gcc now.
> > >
> > > Thanks in advance.
> > >
> > > Best regards
> > >
> > > Byeong-Gi KIM
> > >
>
>

  reply	other threads:[~2014-07-14  8:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14  7:39 BYEONG-GI KIM
2014-07-14  7:52 ` Aravind
2014-07-14  8:10   ` De Lara Guarch, Pablo
2014-07-14  8:29     ` BYEONG-GI KIM [this message]
2014-07-16  8:15       ` Gray, Mark D
2014-07-14  8:32 ` [dpdk-dev] [Dpdk-ovs] " Choi, Sy Jong

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='CAEHt_JbqByL11VQqTxNmAUKQRZiiGzOs2GP=5Qx+k_MT6JJjwg@mail.gmail.com' \
    --to=kimbyeonggi@gmail.com \
    --cc=Dpdk-ovs@lists.01.org \
    --cc=altoarun@gmail.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).