From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v7 4/9] ethdev: Add port representor device flag Date: Wed, 25 Apr 2018 14:23:59 +0200 Message-ID: <5265650.YqjcpsQ2DK@xps> References: <20180328135433.20203-1-declan.doherty@intel.com> <190601101.P8xlxIF3tq@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: qi.z.zhang@intel.com, dev@dpdk.org, Adrien Mazarguil , Ferruh Yigit , Shahaf Shuler To: "Doherty, Declan" Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 405C35B40 for ; Wed, 25 Apr 2018 14:24:02 +0200 (CEST) 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" 25/04/2018 14:17, Doherty, Declan: > On 24/04/2018 8:37 PM, Thomas Monjalon wrote: > > I think dev_capa and dev_flags are the same thing. > > They could be merged. > > Do you have a preference for which one to keep, as dev_flags within > rte_eth_dev_data is widely used by PMDs and passing this same > information out through rte_eth_dev_info makes sense to me? I think a big cleanup in ethdev structures is required. We could avoid copying fields from one struct to the other. But I don't want to block this patch, so go ahead and we will clean this mess later.