From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH] [RFC] ether: standardize getting the port by
 name
Date: Thu, 30 Nov 2017 13:21:26 -0800
Message-ID: <20171130132126.13761c50@xeon-e3>
References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org>
 <20171130091552.3aa6e46c@xeon-e3> <6035648.0D6NuDDM7V@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Yuanhan Liu <yliu@fridaylinux.org>, dev@dpdk.org, Adrien Mazarguil
 <adrien.mazarguil@6wind.com>, Ciara Loftus <ciara.loftus@intel.com>, Kevin
 Traynor <ktraynor@redhat.com>, hemant.agrawal@nxp.com
To: Thomas Monjalon <thomas@monjalon.net>
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 99E561AEF4
 for <dev@dpdk.org>; Thu, 30 Nov 2017 22:21:34 +0100 (CET)
Received: by mail-pg0-f42.google.com with SMTP id b18so3525982pgv.10
 for <dev@dpdk.org>; Thu, 30 Nov 2017 13:21:34 -0800 (PST)
In-Reply-To: <6035648.0D6NuDDM7V@xps>
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 Thu, 30 Nov 2017 18:35:11 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:

> 30/11/2017 18:15, Stephen Hemminger:
> > Some thoughts.
> > 1) Not all devices are PCI; look at recent VMBUS  
> 
> Yes, we need a syntax which works for every devices.
> I suggest to use the prefix "pci:" before the PCI id.
> We need also a prefix and ids for NXP buses.
> We could use "vmbus:" before VMBUS ids.
> How VMBUS ids look like?
> 
> > 2) The name may have to be set before MAC address is determined on boot.  
> 
> I don't understand this comment.
> Do you mean MAC may be unknown when starting DPDK?

The MAC be known by the hardware, but the device would have to be
created before using  hardware to read it.


> 
> > 3) The names themselves are not persistent or human friendly. This is hard
> >    see the effort udev goes to.  
> 
> Yes udev has a syntax to identify devices. It can be inspiring.
> Qemu may also be inspiring:
> 	https://github.com/qemu/qemu/blob/master/docs/qdev-device-use.txt