From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 191C321C5C; Fri, 5 Jan 2018 07:01:58 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 05 Jan 2018 07:01:58 -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=Urzu8TSbMcPSUy4I3sNuPdkKWT NmStOq8udBPhGS254=; b=DHiqf1lADht7tQCs10CJqrdd7U5SUB1QOuq8jNW5rL tFCLHl8Q4PC+v0YYqIqM34G6CfYBZ8gW4g/ifyPF8llBC6mIngCBKleDS5FUsXRh 5GxnBM7zwAsYVOetdAbQmv6u1+UBEoq5WmdJ3jGLjzciMWHPYf4WBcPW9KlRsqDY A= 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=Urzu8T SbMcPSUy4I3sNuPdkKWTNmStOq8udBPhGS254=; b=gwmNxu1QBdbLspfizgzmXR wo7NTuIT+7D85UFahpYxeKE4rolUHYiKY19IBTrwEBUxUutUcBuWggYR350UQFSB jYNWqOc5bn/FrzGrMkdVbOoFOI+dD+u3Q7MGw974pQcVahy+e7eopsLe6O1phlFu xS1Krt/5HsNpg1yWcgWLFsKMTv9kuqd+ANpVixMPyTbfghDR5Cs9bjL8lV7VKBII uPtL+QFYDVDOCPsXMaC4jbloy+/uTHDlKVZqnGwnd30THyEG4Y5G1LvvsihKw9xS PwW6swQG/qMUGo6L7/fqD4XVsEVvz7DIuOPb10/0fEUEqmk2cEtZuPOT9TfF9gXQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id ABCCC24599; Fri, 5 Jan 2018 07:01:57 -0500 (EST) From: Thomas Monjalon To: Finn Christensen Cc: dev@dpdk.org, Yuanhan Liu , Adrien Mazarguil , Ciara Loftus , Kevin Traynor , "stephen@networkplumber.org" , "ferruh.yigit@intel.com" Date: Fri, 05 Jan 2018 13:01:36 +0100 Message-ID: <2746853.LkVxvJSmNi@xps> In-Reply-To: References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org> <3183370.0ufOrFygau@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] standardize device identification X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jan 2018 12:01:59 -0000 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.