From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 5259A23B for ; Tue, 1 May 2018 22:41:12 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B988522896; Tue, 1 May 2018 16:41:11 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 01 May 2018 16:41:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=07Ljdjzo96/CrJd09mq2x9Chx+lvEQauUmj50Ing1Ew=; b=LWtCW GGqFeBqw3WmUs+NFfhRI0cG+mH3jGaoO/aO5/41Du00cJRnvEV/6nHSP+1Ts7w8N wsaxKpX7Mx4H5jLpWpud8NIiYfZh0dlB8ZvhS7sX9qgPzTsJNfm2stbVFiEZcv8G y4neixy6UAPvfoGOmD7R/2vZ/h5RNt8CNlJR/4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=07Ljdjzo96/CrJd09mq2x9Chx+lvE QauUmj50Ing1Ew=; b=DZ84kfwMtj7ZTxy7lJ80fR9/NiQ/PaYcvK8v9Iqb0dGqY UitZsYrZjRdiYkK4HcbBHXVmzLJ8nrrUkBqbBzU8z0GpWKcbfYDcmgaLgbGjezzc NCOgpYuWvpSJ5gWOfMMXi1bIzdMyUH88GJJOZ/rW/GOusF6nwCZT6i5oiP6ETISN 6dPO4Wlx2lrOqTDuUd25veRBtah5YcnR2nmqmKlmrxQtzhkCaZkMxlwAiGTod5xI WuwwKtCMLzQYYqNtGMo5ao2cZYBI4zPCIVAL+l/yPjZGSYJthmFutBkpzSTlCv/o rr3rGZEFmkWsIr28E6HxyJT5IalaVnCds7336AHTg== 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 BFA84E4350; Tue, 1 May 2018 16:41:10 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: declan.doherty@intel.com, ferruh.yigit@intel.com, arybchenko@solarflare.com, bruce.richardson@intel.com, olivier.matz@6wind.com Date: Tue, 01 May 2018 22:41:09 +0200 Message-ID: <3264503.09g30QS5gu@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-dev] ethdev flags and capabilities 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: Tue, 01 May 2018 20:41:12 -0000 Since DPDK 18.05-rc1, we have 2 new fields in rte_eth_dev_info: const uint32_t *dev_flags; uint64_t dev_capa; The field dev_flags (http://dpdk.org/commit/736b30ebf2) is a pointer to rte_eth_dev_data.dev_flags for these bits: RTE_ETH_DEV_INTR_LSC RTE_ETH_DEV_BONDED_SLAVE RTE_ETH_DEV_INTR_RMV RTE_ETH_DEV_REPRESENTOR The field dev_capa (http://dpdk.org/commit/cac923cfea) is an integer for these bits: RTE_ETH_DEV_CAPA_RUNTIME_RX_QUEUE_SETUP RTE_ETH_DEV_CAPA_RUNTIME_TX_QUEUE_SETUP How can we merge them? Should we move the capabilities in rte_eth_dev_data.dev_flags? Or do we want to keep the capabilities in rte_eth_dev_info? Is it OK to use pointers in rte_eth_dev_info or should we make a copy of rte_eth_dev_data fields? We need to take a decision before RC3. Thanks