From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aravind Subject: Re: No "pci_unbind.py" in tools subdirectory Date: Mon, 14 Jul 2014 13:22:03 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: dev-VfR2kkLFssw@public.gmane.org, Dpdk-ovs-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org To: BYEONG-GI KIM Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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 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 >