From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH v8 4/4] ethdev: add control interface support
Date: Fri, 30 Jun 2017 18:06:23 +0100
Message-ID: <8d1fa96e-52e6-9afa-4537-fa7eb79ddc3c@intel.com>
References: <20170526165228.96919-1-ferruh.yigit@intel.com>
 <20170621110651.75299-1-ferruh.yigit@intel.com>
 <20170621110651.75299-5-ferruh.yigit@intel.com>
 <20170621082459.5e127994@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>,
 "Burakov, Anatoly" <anatoly.burakov@intel.com>,
 "Richardson, Bruce" <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31])
 by dpdk.org (Postfix) with ESMTP id 723E57CAF
 for <dev@dpdk.org>; Fri, 30 Jun 2017 19:06:26 +0200 (CEST)
In-Reply-To: <20170621082459.5e127994@xeon-e3>
Content-Language: en-US
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 6/21/2017 4:24 PM, Stephen Hemminger wrote:
> 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.

I didn't get this one, currently interface names are requested from
userspace via IFLA_IFNAME, as dpdk# .