From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by dpdk.org (Postfix) with ESMTP id 67EC780A6 for ; Fri, 12 Dec 2014 14:57:24 +0100 (CET) Received: by mail-pa0-f51.google.com with SMTP id ey11so7353877pad.10 for ; Fri, 12 Dec 2014 05:57:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=BYkgx4L0yicbdALVh9/IMQ/7LZwr5tKPSxWKFpSa3QA=; b=GtFwyFfKc9RKk5DDFYcTWHdcd6rkwiNn087pULe/CMr4TfG/ds0JKmmSubyZan7SrZ AewrFW5iaX6kxDeTlfGR804Jvt79cFqg5iJn6PrWzIBCawtPDCZaZxgexEinHP+wGPjB sINsBvNjkhInneAuoEcDiYGI9bjBLwzoP7PPvx+/BWFKdIrHioWXJjqFKiaRXmjle3vw 0vnxGN8Tfzi7J1QghYAut3QyCvQMaaEP9/YSdmauQGBWIN4SxJylb4LCVmaVeKgZamRW 646I4PW0dGUZPzqo9Z9pGQurplco2utEMcRqZEp6n6bnlMNnGVFOWnrEBTqp8Hn/rFy8 Ji5g== MIME-Version: 1.0 X-Received: by 10.66.147.102 with SMTP id tj6mr26691844pab.95.1418392643515; Fri, 12 Dec 2014 05:57:23 -0800 (PST) Received: by 10.70.4.162 with HTTP; Fri, 12 Dec 2014 05:57:23 -0800 (PST) In-Reply-To: References: Date: Fri, 12 Dec 2014 14:57:23 +0100 Message-ID: From: Sachin Sharma To: dev@dpdk.org, marc.sune@bisdn.de Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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:57:24 -0000 Hi Marc, I have limited number of nodes (Linux nodes) in my testbed. So, I wanted to use veth interfaces for creating some of dpdk nodes in my nodes. You said that I can use KNI interfaces for this purpose. I am very new to KNI terminology. Could you please redirect me to a tutorial to create links with KNI interfaces and then adding those KNI interfaces into dpdk? Thanks & Regards, Sachin. 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 On Fri, Dec 12, 2014 at 2:34 PM, 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? > > > Regards, > Sachin. >