From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ee07b291@gmail.com>
Received: from mail-yw0-f180.google.com (mail-yw0-f180.google.com
 [209.85.161.180]) by dpdk.org (Postfix) with ESMTP id 51B6D293C
 for <dev@dpdk.org>; Wed, 30 Mar 2016 19:20:10 +0200 (CEST)
Received: by mail-yw0-f180.google.com with SMTP id g3so66779163ywa.3
 for <dev@dpdk.org>; Wed, 30 Mar 2016 10:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to;
 bh=yFCclogHqfb+XJY2iFJIssbQtMsI2lgvplwDi/BWYwc=;
 b=QsuUrwiDRTeeB7coVAfhDoFNxaNtH0rVLL4gxsjPeZkk5i6c4btJYTRR5Wt96PK+5p
 903Jxy3XyFesTvClByDWPzEHIPrGlvoyh7PzAt3JPwQ2WJOCYKfW9dJEOxBV7Gj9r39i
 zkitV2kyDSFeJLaArz0ykvMR4JEngWes/p3a63Kpn1tFF43hrC7EJZ/koaNqthUNd3oo
 SZxS66oikI2r1vlZavlIdMqJopOQIKDoEjgk2Zknpx/32dAtzY1BZkr5wp3CQNhtwTBL
 pW76wTcyN/sSL9TaGzxoUZSJqfCfyTl6cWwYOT6g4yQHd24F/Xyo3MvHujqLv2hlGpkl
 OKuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to;
 bh=yFCclogHqfb+XJY2iFJIssbQtMsI2lgvplwDi/BWYwc=;
 b=I6CgCbU56gkFvIirTM5h9ku6H0L0W0CgVISJdsj8nAb4CDlDdM0JFMkryr3hlWLio0
 Fn4hVF2Kmj1kuCm742qtICndhwZ9tsA80rkI4rilfcV1uh3nq1jx1FJd0DYdMY3LEhZJ
 YwGyNdyBgCTtovVGcZE4SZmbngIjqOICNTly8THajjcqer6Lp3+M949e3x2ffTR7Zabe
 yvMf/V012GjfWqr7Za4d/Xj1k0yfD7NPWzH3260+x4QmOVlMPXF0a5TBy8UV5jT1UCrW
 06gjc7qHWgQhGValnp86Jcw2PkOC2N0kq900SzWzKryClyBXUIEI5VMQeXCjikOcZZN6
 AEXQ==
X-Gm-Message-State: AD7BkJLD7n2SGzoZA239S8wa+/VHFQsxkrO5sCrpjzFhQ0MmhTTLuecP/d0z+c1MgeVwt1KKmv8cenRndOlKEw==
MIME-Version: 1.0
X-Received: by 10.37.57.202 with SMTP id g193mr4713366yba.41.1459358409639;
 Wed, 30 Mar 2016 10:20:09 -0700 (PDT)
Received: by 10.129.70.194 with HTTP; Wed, 30 Mar 2016 10:20:09 -0700 (PDT)
Date: Wed, 30 Mar 2016 10:20:09 -0700
Message-ID: <CANmyKO5Cs0NTmfT8EPApHp7y7=wVPMXNtsm8_Qnuk47ZZd0h4g@mail.gmail.com>
From: ALeX Wang <ee07b291@gmail.com>
To: dev@dpdk.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2016 17:20:10 -0000

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,
-- 
Alex Wang,