From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] [RFC] ether: standardize getting the port by
	name
Date: Thu, 30 Nov 2017 22:44:58 +0100
Message-ID: <1581666.Z35b0Iulko@xps>
References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org>
 <6035648.0D6NuDDM7V@xps> <20171130132126.13761c50@xeon-e3>
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: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 592311B160
 for <dev@dpdk.org>; Thu, 30 Nov 2017 22:45:00 +0100 (CET)
In-Reply-To: <20171130132126.13761c50@xeon-e3>
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>

30/11/2017 22:21, Stephen Hemminger:
> 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.

Indeed, it is a problem if we want to use this syntax for blacklist.


> > > 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