From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31]) by dpdk.org (Postfix) with ESMTP id 05FF680A1 for ; Fri, 12 Dec 2014 14:41:40 +0100 (CET) Received: from [172.16.250.156] (unknown [172.16.250.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.bisdn.de (Postfix) with ESMTPSA id 2252EA09C2 for ; Fri, 12 Dec 2014 14:41:39 +0100 (CET) Message-ID: <548AF08F.1080709@bisdn.de> Date: Fri, 12 Dec 2014 14:41:35 +0100 From: Marc Sune User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 MIME-Version: 1.0 To: dev@dpdk.org References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] How to add veth interfaces in dpdk X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 13:41:40 -0000 On 12/12/14 14:34, Sachin Sharma wrote: > Hi all, > > I have created veth interfaces using command "sudo ip link add veth1 type > veth peer name veth2". However, when I use command "sudo > ./tools/igb_uio_bind.py --force --bind=igb_uio veth1" to add veth into > dpdk. It gives me an error that "Unknown device: veth1. Please specify > device in "bus:slot.func" format". I do not see even veth interfaces using > command "sudo ./tools/igb_uio_bind.py --status". Is there any way that I > can add these interfaces into dpdk? veth are software interfaces, meaning there is no real NIC behind. That's why you cannot bind them to igb_uio. You can use KNI interfaces for communicating a DPDK application with the kernel interfaces and viceversa. There is an overhead on doing so, but whether this is an appropriate solution or not, depends on your use case. What do you plan to do? Marc > > > Regards, > Sachin.