From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v8 4/4] ethdev: add control interface support
Date: Wed, 21 Jun 2017 08:24:59 -0700
Message-ID: <20170621082459.5e127994@xeon-e3>
References: <20170526165228.96919-1-ferruh.yigit@intel.com>
 <20170621110651.75299-1-ferruh.yigit@intel.com>
 <20170621110651.75299-5-ferruh.yigit@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org, anatoly.burakov@intel.com, Bruce Richardson
 <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pg0-f42.google.com (mail-pg0-f42.google.com [74.125.83.42])
 by dpdk.org (Postfix) with ESMTP id D21B42BC3
 for <dev@dpdk.org>; Wed, 21 Jun 2017 17:25:01 +0200 (CEST)
Received: by mail-pg0-f42.google.com with SMTP id f127so1713958pgc.0
 for <dev@dpdk.org>; Wed, 21 Jun 2017 08:25:01 -0700 (PDT)
In-Reply-To: <20170621110651.75299-5-ferruh.yigit@intel.com>
List-Id: DPDK patches and discussions <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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Wed, 21 Jun 2017 12:06:51 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> To have the support corresponding kernel module (UNCI) needs to be
> inserted.  If kernel module is not there, application will run as
> it is without kernel control path support.
> 
> When UNCI module inserted, running application creates a virtual Linux
> network interface (dpdk$) per DPDK port. This interface can be used by
> traditional Linux tools.
> 
> If Userspace Network Control Interface (UNCI) kernel module
> (rte_unci.ko) inserted, virtual interfaces created for each DPDK port
> for control purposes.
> 
> Created interfaces are named as dpdk#, like:
> 
>     $ ifconfig dpdk0; ifconfig dpdk1
>     dpdk0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
>             ether 90:e2:ba:0e:49:b9  txqueuelen 1000  (Ethernet)
>             RX packets 0  bytes 0 (0.0 B)
>             RX errors 0  dropped 0  overruns 0  frame 0
>             TX packets 0  bytes 0 (0.0 B)
>             TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
>     dpdk1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
>             ether 00:1b:21:76:fa:21  txqueuelen 1000  (Ethernet)
>             RX packets 0  bytes 0 (0.0 B)
>             RX errors 0  dropped 0  overruns 0  frame 0
>             TX packets 0  bytes 0 (0.0 B)
>             TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


If you get the sysfs network links correct, then udev should be able to
generate peristent network names.