From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] [RFC] ether: standardize getting the port by name Date: Thu, 30 Nov 2017 18:35:11 +0100 Message-ID: <6035648.0D6NuDDM7V@xps> References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org> <20171130091552.3aa6e46c@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Yuanhan Liu , dev@dpdk.org, Adrien Mazarguil , Ciara Loftus , Kevin Traynor , hemant.agrawal@nxp.com To: Stephen Hemminger Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 604C07CB6 for ; Thu, 30 Nov 2017 18:35:13 +0100 (CET) In-Reply-To: <20171130091552.3aa6e46c@xeon-e3> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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? > 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