From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: standardize device identification Date: Fri, 05 Jan 2018 13:01:36 +0100 Message-ID: <2746853.LkVxvJSmNi@xps> References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org> <3183370.0ufOrFygau@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Yuanhan Liu , Adrien Mazarguil , Ciara Loftus , Kevin Traynor , "stephen@networkplumber.org" , "ferruh.yigit@intel.com" To: Finn Christensen Return-path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 9D6FC2951 for ; Fri, 5 Jan 2018 13:01:59 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 05/01/2018 12:09, Finn Christensen: > From: Thomas Monjalon > Which property can help to distinguish Napatech ports? > Can you use class=eth,dev_port=X ? > The dev_port property will use /sys/class/net/DEV/dev_port on Linux. Is it > OK for you? > > Actually, what we were thinking of was using the mac property in the class > category to distinguish our ports. > For instance: > -w bus=pci,id=0000:01:00.0/class=eth,mac=00:11:22:33:44:55 > or simply: > -w class=eth,mac=00:11:22:33:44:55 The problem with the mac property is that it cannot be used for white/blacklisting in DPDK because the MAC is not known before port initialization. > We will not be able to support the dev_port property, that will not work for us. > At least not for now.