From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f181.google.com (mail-pf0-f181.google.com [209.85.192.181]) by dpdk.org (Postfix) with ESMTP id 209C92C35 for ; Wed, 15 Mar 2017 06:24:11 +0100 (CET) Received: by mail-pf0-f181.google.com with SMTP id w189so3953043pfb.0 for ; Tue, 14 Mar 2017 22:24:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=gOYda3Q3tpecvgx8AQLCGxwP0UJVmG7Vu54iOvJ3GTo=; b=nuYhNcpPfKqES6S2a7vqbwZ4Fy1wtexo0yPQpaaa/JnHQi4C9ij1+qQRG8XVbAbred IUHT/lzmO07H/j5fIG6a2wF/bdHLeSQUPNBh7ofeoe0VOWjMv9Tsu6DtECmOajKbYvhh x1q7gp6pp4QajeP29RopdhOTBWEysUfoVl6owb3vkrou5zVCbpYOOHoLDyTr83NQ1bLu Aqeu6xdX8SH7qcV+GLfycgR70QYAUVFrmt3FVzmLLHZLiRNFTDUts6TuGrsSOmPHcR4z qSLNMsUebs4Ns4HWzxgLAlB+uhFYih3R5tEOe7yVHBwNF/7mThb6jKXqF02LwqBiw/PB pJhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=gOYda3Q3tpecvgx8AQLCGxwP0UJVmG7Vu54iOvJ3GTo=; b=FLD7MHxKs+6Wf91ycy9heMXuxBwxM5ecKNUPsG+RQeUdpvD1+hM8/rOfoL1KZq3Ucf /DeYWiXkb4S0yDXYcIqdzJCCqZfToU3dLUHS6biDcbHIivKntjGpvSRfsdcV7BzXoUW5 yQC2CulCQ5ILk34gonY37auvfD7MHksmS1ap4wnl3lldA0nDclVig7q3XOgY9csCKrAB +0CPQSwfpcBvmMgRC512pNUU4rW8CIXGzwQbjx+zHpNuX1fq/nJE08tGWqrNmvrjYTT7 +PoEV6qN0StCyj6rVUGcnUn+SBxxsHCWIjsu4aLpXYyFIgGlj9IahO3NNrdO37Mut90A J1yw== X-Gm-Message-State: AFeK/H2ZQEJQAFhgdQC1eNmkMeTtofez0KUoZvJ0Hve33zgF3Owt4zBKrPsvvp48WNVlYw== X-Received: by 10.99.224.69 with SMTP id n5mr1562232pgj.113.1489555450257; Tue, 14 Mar 2017 22:24:10 -0700 (PDT) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id q73sm1189639pfa.129.2017.03.14.22.24.09 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 14 Mar 2017 22:24:10 -0700 (PDT) Date: Tue, 14 Mar 2017 22:24:02 -0700 From: Stephen Hemminger To: Bruce Richardson Cc: Ferruh Yigit , raman geetha gopalakrishnan , dev@dpdk.org, users Message-ID: <20170314222402.1648a719@xeon-e3> In-Reply-To: <20170315044502.GA7360@bricha3-MOBL3.ger.corp.intel.com> References: <8a209536-17fc-790c-527f-5354a185c2e6@intel.com> <20170315044502.GA7360@bricha3-MOBL3.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] [dpdk-dev] Reg DPDK with unsupported NIC X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2017 05:24:11 -0000 On Wed, 15 Mar 2017 04:45:03 +0000 Bruce Richardson wrote: > On Tue, Mar 14, 2017 at 12:07:42PM +0000, Ferruh Yigit wrote: > > On 3/14/2017 9:28 AM, raman geetha gopalakrishnan wrote: > > > Hi , > > > > > > Please find my query, Currently i am planning to develop DPDK APP (linux > > > env). I do not have DPDK supported NIC. Till then i would still like to > > > develop DPDK APP and want DPDK to use OS interface to TX/RX packets from > > > NIC. How can i make it? > > > > > I went through KNI and my understanding is you > > > cannot use it - is this correct? > > > > You can use it. KNI does not require a physical device at all. > > > > But with the KNI support in main tree, you need to use KNI specific > > APIs, - which KNI sample app shows. > > > > With the KNI PMD in next-net tree, it is possible to use KNI as any > > other device. > > > > Just my 2c. While you can indeed use KNI here, I think I would recommend > pcap or AF_PACKET as my first-choice options, with TAP also a > possibility too, as Keith has already suggested. > > /Bruce Other than development environment, why would you want to use DPDK with AF_PACKET or TAP? It will be slower than kernel networking and with KNI doubly slow.