From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com [209.85.128.182]) by dpdk.org (Postfix) with ESMTP id 7F23614EC for ; Mon, 6 Feb 2017 12:05:34 +0100 (CET) Received: by mail-wr0-f182.google.com with SMTP id k90so21474216wrc.3 for ; Mon, 06 Feb 2017 03:05:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=TX+uKLOFNvKPgoCm1UQpst+n7gRLw+I9DvWJgr04Bog=; b=GkVxv1A0rk/yKCm3WPbBHuXh4DcBBUKbmsp8fl0Wk1WL5Cr9+oxyvGuHYQctr5Ng2F TzanbC8e4KFOeiITbiBWKH9TL3Th0XfY2CHUjELd/9JvL7NYbn6BSExb6paNLVqqKkog gjLHI3gkaxvpMxMbAsrODOiB9pyHEgil+tI4hng0USF8ox+ozQF7UhEE1Ae6XpabhSdm iijtJzYze185csf55HqtsetU4RCmBgej8v/canjP2Eznc9dAv/qvxcHW/69ZwF7/fUWV 9DbWlee62PDW6swb5pdR43VsQ6uQJWwObn3XjZR2SndyEc7YZYP9dE12R45eStRd+UST z5hA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=TX+uKLOFNvKPgoCm1UQpst+n7gRLw+I9DvWJgr04Bog=; b=Q8FjS/OHeeg72dAembTxwl6gJ+kXI5n9tuOXhvYofiqb4io1pYPL8LE+YQi40IC1pq wZF80D3m80fdwMx5MWohsXhwJNNlzAZTQ7xWgark0/D9tYJC+Emy+Dj6dlxUJqj9SQTG SRtHZbtETph6BRsF1qQ53hntB/SI7qpu3cWfVKXuGzpQYnmMdrRar4mLGQbwyALkCd1Q 0x9tti5VzPavumIuSwHnkMiTQ7lETrCdjGm+UBTtOwh43/bR1NG5sbbjlfbyZmKjWb17 /D8l0VzOk7LZCSxgYZ7V+S5bC/Qn2iutG0OCPQCyiSOzXWbttld5KeyeK22OF6p/P+cE aNsA== X-Gm-Message-State: AIkVDXJO2GMFref4pxKmW2hjwwnlOmDJ2u1F8fdUaDRnEzFQ6DywJZ9KR+M5J0rxnYQWiQN2Qy6q2C4bFIXy+g== X-Received: by 10.223.154.114 with SMTP id z105mr8715960wrb.89.1486379132755; Mon, 06 Feb 2017 03:05:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.238.147 with HTTP; Mon, 6 Feb 2017 03:05:12 -0800 (PST) In-Reply-To: <790E2AC11206AC46B8F4BB82078E34F806276F93@EXUSMBX02.AD.MLP.com> References: <790E2AC11206AC46B8F4BB82078E34F806276F93@EXUSMBX02.AD.MLP.com> From: Take Ceara Date: Mon, 6 Feb 2017 12:05:12 +0100 Message-ID: To: "Lazarenko, Vlad (WorldQuant)" Cc: "users@dpdk.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] KNI drive without supported NICs? 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: Mon, 06 Feb 2017 11:05:34 -0000 Hi Vlad, On Sun, Feb 5, 2017 at 6:34 PM, Lazarenko, Vlad (WorldQuant) wrote: > Gentlemen and gentleladies, > > I am trying to get the KNI working on my dev box. So I've loaded the rte_= kni.ko module and made sure /dev/kni has correct permissions. But when I am= trying to run the KNI example, it fails with "No supported Ethernet device= found" error: > > $ build/kni -n 4 -c 0xf0 -- -P -p 0x3 --config=3D"(0,4,6),(1,5,7)" > EAL: Detected 24 lcore(s) > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > EAL: probe driver: 8086:10d3 net_e1000_em > EAL: Error - exiting with code: 1 > Cause: No supported Ethernet device found > > My dev box does not in fact have supported NICs. But my understanding abo= ut KNI was that it allows to access Linux network stack trough the KNI kern= el module, where applications create a virtual Ethernet devices (i.e. /sys/= class/net/vEth*), thus there is no need for a real supported NIC or taking = over the entire NIC. > > On the other hand, the example application calls rte_eth_dev_count() firs= t, which in my case returns 0, and exits. > > Is my understanding about what KNI actually is wrong? Or am I missing som= ething else? > As far as I know the KNI sample app actually forwards traffic to/from the kernel and a physical port therefore the check for physical interfaces. If you want to use KNI for something else there's nothing stopping you from starting a DPDK app and adding a KNI interface without having a real NIC bound to DPDK. I don't have a better example right now but, if you want, you can take a look at how we do it in warp17 (using DPDK) when you start it without any physical interfaces: https://github.com/Juniper/warp17#using-kernel-network-interface-kni-interf= aces If you look at the HTTP example there we actually start the application without any physical interfaces (only one KNI): ./build/warp17 -c FC3 -n 4 -m 32768 -- --kni-ifs 1 > Thanks, > Vlad Hope this helps.. Regards, Dumitru > > > > #########################################################################= ########## > > The information contained in this communication is confidential, may be > > subject to legal privilege, and is intended only for the individual named= . > > If you are not the named addressee, please notify the sender immediately = and > > delete this email from your system. The views expressed in this email ar= e > > the views of the sender only. Outgoing and incoming electronic communica= tions > > to this address are electronically archived and subject to review and/or = disclosure > > to someone other than the recipient. > > #########################################################################= ########## --=20 Dumitru Ceara