From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f180.google.com (mail-yw0-f180.google.com [209.85.161.180]) by dpdk.org (Postfix) with ESMTP id 3F9DF8E74 for ; Thu, 31 Mar 2016 17:22:52 +0200 (CEST) Received: by mail-yw0-f180.google.com with SMTP id g3so101497592ywa.3 for ; Thu, 31 Mar 2016 08:22:52 -0700 (PDT) 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 :cc; bh=pGsMl2QxcnfKvemNizaiALj905owAlv3K4Qr36gCSDk=; b=VLdN8V4MDc10Y57hAztEzCikMIrXGjjm98nvQOS6GUv6RnW2SbdvKSxaE8D+1SJPwa TDivfoT6YClAFSooM9hs/VrLEMhrzj5EYEnDRf12ZJztVO6yf9g1Wy0flvPulj9FuQWQ zbSZLgjpDOqOOjitKKuRn79V31zSyaJJG7fqyIKUUQWU9ExV3K0Lavu+Fx3B2RU2siv1 1HOPd4yuxcswBr11Pt8T8H4hb3ynbgdZP0vBeDKNif5XNrxC9+iSv3e7EWMrL+vev+Sm zvhrt4SykwTgKGfZ10qo2unMp87/km/7eYUHgk9eX6rTa6FpL4y9ouP3Xm1LrZ9ysEX1 yNsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=pGsMl2QxcnfKvemNizaiALj905owAlv3K4Qr36gCSDk=; b=kPahsxVsN+JBXN9SKnMdfcFqX1oCTF/WuTLvjiN7OjUm5exLXbdar6zCQktx/YqS/Y 4kBak5RMrcDAqYRJ6ValQ35w3gWqjfXGcjDvy4CZRZe/ndf/Nv+YR2QKNhQnNkKmOpMb 99M5miuMdNtvUZX3s4zfBaWawQST2tqD9MCPApZcdyofm9HsvzwppgJSFaJxldDVBglq 8fnUSIRoqOtxwuUDHTAr4LCEw2NN9Sjie+Yi5N79S3uF1D8SAE16sBtmRSbxlPEAWwug cijWxmi8APFx9lfxVIjVkTeJni9mWOoLHRCBZKafV6UAaZg4EmOiIZnv5nBJPpht1Q73 FqJQ== X-Gm-Message-State: AD7BkJIijn4Mn9Wl1UNN1Q8gw136zvaaNv/OtYjZ7cSwrohTprJYQ3zEHXNgrYE1h4t76X+xqskFiaEbJf2/vQ== MIME-Version: 1.0 X-Received: by 10.37.91.134 with SMTP id p128mr8143256ybb.69.1459437771586; Thu, 31 Mar 2016 08:22:51 -0700 (PDT) Received: by 10.129.70.194 with HTTP; Thu, 31 Mar 2016 08:22:51 -0700 (PDT) In-Reply-To: <56FCF415.6090301@intel.com> References: <56FCF415.6090301@intel.com> Date: Thu, 31 Mar 2016 08:22:51 -0700 Message-ID: From: ALeX Wang To: Ferruh Yigit Cc: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Must kni be associated with a dpdk port? 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: Thu, 31 Mar 2016 15:22:52 -0000 Thx a lot, for the answer,! Exactly what I'm looking for,~ On 31 March 2016 at 02:55, Ferruh Yigit wrote: > On 3/30/2016 6:20 PM, ALeX Wang wrote: > > Hi, > > > > I want to use 'rte_kni_alloc()' to create a kernel iface and > > use it to test application rx. From the api and example in > > 'examples/kni/main.c', i saw the 'conf' argument is assigned > > with pci info of a dpdk port. > > > > Want to ask if this is compulsory... Must kni always be > > used together with a dpdk port? > > > > Thanks, > > > > Hi Alex, > > You don't have to associate kni with dpdk port. > > pci info is required for ethtool support, if you are only interested in > data transfer, you don't have to provide pci information. > > Regards, > ferruh > -- Alex Wang, Open vSwitch developer