From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ee07b291@gmail.com>
Received: from mail-yw0-f177.google.com (mail-yw0-f177.google.com
 [209.85.161.177]) by dpdk.org (Postfix) with ESMTP id 41A86914
 for <users@dpdk.org>; Wed, 30 Mar 2016 20:14:55 +0200 (CEST)
Received: by mail-yw0-f177.google.com with SMTP id g3so68645465ywa.3
 for <users@dpdk.org>; Wed, 30 Mar 2016 11:14:55 -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=b5rIAWmdxrcAh19BNR6InvGzzPrZltcRFE54NgLqKXE=;
 b=oOkoGOFU0WL7lgmKBaTN25jIURGQnFD7syxa/Mg0SuKbkbGyGgXffNqLvWdRLhj6vs
 fCW/LgzKZP+Hg0f2UjLWfAU2vsA+Y9BpWoZ4hvBJ0/JdjxafKg/GFTbOxLCXMoP9B79I
 M+bk8T6wvVDXR8qVdMRscxQ9tiZ5fHZU9dc1taFffEbkCIrFsgnzU8WefD2p47Rhu5gj
 uFfB5o4qIwxqJXCrscXin05JKRu1I7VQvvJ3NiubvYn6lBbf7/FijPm8mAN4z6YqkipU
 ep5LJLcwld/N7N0ODmEtKZHPVE+osetmdyScyTpyrqEdJUr5AsTG8Qj9Vgth0tOnyimh
 Y9Ow==
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=b5rIAWmdxrcAh19BNR6InvGzzPrZltcRFE54NgLqKXE=;
 b=NfoqrRmnuwuKEN9+FLTFfFeR85Bk77tRht1UyFj7WwivT7zAze8mHUOmqDrcoPIHC4
 EaMCG/AeIlMiJNgabkCy34riJMMsKVgFAkLZo+o4PqUGQ7DEdvwQ8pFSkOGjcEN21YUs
 NUozESkMFpm1d7fbGI3gWhNr0kR7CzgGD4z65sCR52+Kvr7dyByoctvudxmHAUka7y83
 YxGtI6G/0o5UkenpakM5GZBsfsFtuEAdv1o9KTP9glT/Hfr4X/31Nf9h/AJFKq+Llnkd
 aNTpL6levP5jD1nOjsgb4P6IsrkWOTAA5f2Tuh7GIPC8s+Ez9nvx0u8zsOTEDnXdGKNL
 HM0g==
X-Gm-Message-State: AD7BkJKeyqu+PfryHK5Kx/As6qNayxTymdi7Oy8W9KKjL2QB0bgkUdF5ukNCeLXzkXHKPRlcJctyYgVCV1Tp/g==
MIME-Version: 1.0
X-Received: by 10.37.57.202 with SMTP id g193mr4884373yba.41.1459361694787;
 Wed, 30 Mar 2016 11:14:54 -0700 (PDT)
Received: by 10.129.70.194 with HTTP; Wed, 30 Mar 2016 11:14:54 -0700 (PDT)
Date: Wed, 30 Mar 2016 11:14:54 -0700
Message-ID: <CANmyKO77eNM34m7hO-u+ODj-+sZA5vzTNmz7SDPA-kBD9Jvh-A@mail.gmail.com>
From: ALeX Wang <ee07b291@gmail.com>
To: users@dpdk.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-users] Must kni be associated with a dpdk port?
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2016 18:14:55 -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,