From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id B416A5F2A for ; Thu, 20 Sep 2018 18:17:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F101221F57; Thu, 20 Sep 2018 12:17:15 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 20 Sep 2018 12:17:15 -0400 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=GQnxug2qoPsEj6zXDaNK9wOCch JshUenmuhCYUbTUxc=; b=WcYUwfNGCfJu8YfCahThRtkPfxqdbH0c93uvUFVu6m TalBkbyCqhQuysxfrU/1ftCSDzNWDgS3Aa6DaQf5Dx2Hjd++rhKdpzMkZihhOZ1d It1YtU93zB0zsJdXHaUbCPPTYk42L0kKafOASYDgMNQP2G5UCG9wCMXuOihcNekL 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=fm3; bh=GQnxug 2qoPsEj6zXDaNK9wOCchJshUenmuhCYUbTUxc=; b=uWjpIqnCeVVybJOGx9hbo3 ulInFjkuyzdtZFboK3PlI6W1eIdg+KMI2pDozGHU0+kvquFScEXHYdmOhEoI+8sF FU/pRxYzedliztAX0Znn0ni24sqNehB+G1MHgiI0At0elxcb80Faanfvt/3gW1jL 7N1EtFZTfrTof23wYqS6oDB0s/nWvYdUgKI1pJX2HX8rR1xksiyV5mvQyJlCTKRv MJ9J9lmXbHSBRtYjWQTg9XtFTjCD3DfT43rKzyrp9Uu1bwcPLSrkG/kJNCMl2Wyi aPJm/WqxY18BuPe3846PXLqbbd2nrspJUOTZ5f0gs54XRWtNV0ymn44+Lef2tFDw == X-ME-Proxy: 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 A29AEE4506; Thu, 20 Sep 2018 12:17:14 -0400 (EDT) From: Thomas Monjalon To: Gaetan Rivet Cc: dev@dpdk.org, arybchenko@solarflare.com Date: Thu, 20 Sep 2018 18:17:13 +0200 Message-ID: <6077733.FS8kXFb8lC@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 07/13] ethdev: add device matching field name 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: Thu, 20 Sep 2018 16:17:16 -0000 19/09/2018 18:03, Gaetan Rivet: > The eth device class can now parse a field name, > matching the eth_dev name with one passed as > > "class=eth,name=xxxxxx" I am not sure what is the purpose of the "name" property. I think we should not need it to choose a port by its ethdev name. If you are thinking about a vdev, we can use the rte_device name (at bus level).