No "pci_unbind.py" in tools subdirectory

No "pci_unbind.py" in tools subdirectory

[BYEONG-GI KIM]

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

Re: No "pci_unbind.py" in tools subdirectory

[Aravind]

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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
>

Re: No "pci_unbind.py" in tools subdirectory

[De Lara Guarch, Pablo]

> -----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
> >

Re: No "pci_unbind.py" in tools subdirectory

[BYEONG-GI KIM]

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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>:

> > -----Original Message-----
> > From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of Aravind
> > Sent: Monday, July 14, 2014 8:52 AM
> > To: BYEONG-GI KIM
> > Cc: dev-VfR2kkLFssw@public.gmane.org; Dpdk-ovs-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > 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
> > >
>
>

Re: No "pci_unbind.py" in tools subdirectory

[Gray, Mark D]

> 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
> 


Try this, 

https://lists.01.org/pipermail/dpdk-ovs/2014-June/001120.html

Or you could  the latest 'development' code

> 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
> > > >
> >
> >

Re: [Dpdk-ovs] No "pci_unbind.py" in tools subdirectory

[Choi, Sy Jong]

Hi Mr. Kim,

I think DPDK r1.6 from dpdk.org has change certain file naming. I think it is ok to use the igb_uio_bind.py.
Sometime, I would modprobe –r ixgbe to remove some confusion on the binding. And only load igb_uio.ko from DPDK.


Regards,
Choi, Sy Jong
Platform Application Engineer

From: Dpdk-ovs [mailto:dpdk-ovs-bounces@lists.01.org] On Behalf Of BYEONG-GI KIM
Sent: Monday, July 14, 2014 3:39 PM
To: Dpdk-ovs@lists.01.org; dev@dpdk.org
Subject: [Dpdk-ovs] No "pci_unbind.py" in tools subdirectory

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