From: Aravind <altoarun@gmail.com>
To: BYEONG-GI KIM <kimbyeonggi@gmail.com>
Cc: dev@dpdk.org, Dpdk-ovs@lists.01.org
Subject: Re: [dpdk-dev] No "pci_unbind.py" in tools subdirectory
Date: Mon, 14 Jul 2014 13:22:03 +0530 [thread overview]
Message-ID: <CALySL4QofauOXQmavksDH6+SEtoLtPEb=fQNFmw9nY4jT+8M=w@mail.gmail.com> (raw)
In-Reply-To: <CAEHt_Jb2Ae-23V3FDFwm30M-wHmhmP0U8smZsFdFD9riHpTXDQ@mail.gmail.com>
Hi,
You should be using igb_uio_bind.py , have a look at the quick start guide
: http://dpdk.org/doc/quick-start
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
>
next prev parent reply other threads:[~2014-07-14 7:51 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 [this message]
2014-07-14 8:10 ` De Lara Guarch, Pablo
2014-07-14 8:29 ` BYEONG-GI KIM
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='CALySL4QofauOXQmavksDH6+SEtoLtPEb=fQNFmw9nY4jT+8M=w@mail.gmail.com' \
--to=altoarun@gmail.com \
--cc=Dpdk-ovs@lists.01.org \
--cc=dev@dpdk.org \
--cc=kimbyeonggi@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).