From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
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)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id C91D3209CD;
 Thu, 30 Nov 2017 16:44:59 -0500 (EST)
Received: from frontend2 ([10.202.2.161])
 by compute1.internal (MEProxy); Thu, 30 Nov 2017 16:44:59 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=mesmtp; bh=/wVPeY1vwTg1BTcajHENffvbV9
 HgXNx8tGj1kCv0sPc=; b=Cz2MW11bFKJv29pfS4XfNvbfXUTgv26i7WXC6h7hTk
 1m+UZRUKuV4ypMI6ZbFaXkm0Yte5zMkFN4ogzR6zwffBKY5O49vu8F8ZwlSW3Ea1
 wqn/R824oto+E2EnAIBp5uQ0veOUehtgpsVUD00DW7P1o5oRtUkl055x7z1pZ5o4
 Q=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=/wVPeY
 1vwTg1BTcajHENffvbV9HgXNx8tGj1kCv0sPc=; b=qolInGYqg55Jd5pxCMfnK4
 9GNI/+1vq3ystmYdprObwyUXhBv5pxwSA/NbFtr8mLmiW/7Abq9a3aY8V9oL2Qxj
 tcOxJnR6ISsEZ/gbWiu4Kq70/m1FkFM6u74+Pmv/VIIppWh+9hmiKqmjwbZi5eM2
 Qt0ttrpURmAPDGbrMEBFOhiGd97dk/AN8cVJo2nuN80IoGsfwY5uv4N+z67Svqfk
 etHaaic6RpXXdlJcuTJrFnccRqpBvtmQFq3lZn1S+5JRdGwLuQBu91qcmr0T+cgd
 JH16BlQdbknEglz2dCgCmCHuLpq6Xa90GXAYPOveHASDpbxz3cp13P0Ts5Xj+GHw
 ==
X-ME-Sender: <xms:23sgWuuKmywEymIEgwI26sdkr_u_4PulON1sr9eDngZw6uj4hqMZew>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 7456724ED6;
 Thu, 30 Nov 2017 16:44:59 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
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
Date: Thu, 30 Nov 2017 22:44:58 +0100
Message-ID: <1581666.Z35b0Iulko@xps>
In-Reply-To: <20171130132126.13761c50@xeon-e3>
References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org>
 <6035648.0D6NuDDM7V@xps> <20171130132126.13761c50@xeon-e3>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH] [RFC] ether: standardize getting the port by
	name
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Thu, 30 Nov 2017 21:45:00 -0000

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