From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4FCAAA00C4; Fri, 30 Sep 2022 20:46:28 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3B8C84281E; Fri, 30 Sep 2022 20:46:14 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mails.dpdk.org (Postfix) with ESMTP id 348554003F for ; Fri, 30 Sep 2022 20:46:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1664563571; x=1696099571; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=J84XvCMn8Pua3sjChG0QlXo7Of6L5cJVx0EThY2wtAQ=; b=c1C+Nv5C/cgDvWxixkWYwSZtwD0dI+HMlI3NRVKS6ucaLFQJFnJSZHLT sJ/rEbSVTXt423n4vm7HK/b0ByEOO4p+sy6o3mHAKXXURrx/9mf53XPDU iSdwYtshDNT361ML+8qGbKzWnluuuNuRb++uczlIPcGPoqZzr5gEP9gMb glverAEdCbwnc4e/fvJ0ZLBmlIzlHdEWiTsHHXV0t4UOepJf56tiM9pjQ HaFb1cc+7gDnO7FSWWf3SOrfaBtBJSA/NNCVgpA+jhW/jc3X2ehnQ2mcT nERuNgFUTyuzXMleS99ImB5XKBvzA7g3x3eB7UseV56G8P2bq6DsWstCC Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10486"; a="289424031" X-IronPort-AV: E=Sophos;i="5.93,358,1654585200"; d="scan'208";a="289424031" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Sep 2022 11:46:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10486"; a="951650870" X-IronPort-AV: E=Sophos;i="5.93,358,1654585200"; d="scan'208";a="951650870" Received: from unknown (HELO icx-npg-scs1-cp1.localdomain) ([10.233.180.245]) by fmsmga005.fm.intel.com with ESMTP; 30 Sep 2022 11:46:08 -0700 From: Nicolas Chautru To: dev@dpdk.org, thomas@monjalon.net, gakhil@marvell.com Cc: maxime.coquelin@redhat.com, trix@redhat.com, mdr@ashroe.eu, bruce.richardson@intel.com, david.marchand@redhat.com, stephen@networkplumber.org, mingshan.zhang@intel.com, hemant.agrawal@nxp.com, Nicolas Chautru Subject: [PATCH v10 3/7] bbdev: add device info on queue topology Date: Fri, 30 Sep 2022 11:46:01 -0700 Message-Id: <20220930184605.47655-4-nicolas.chautru@intel.com> X-Mailer: git-send-email 2.37.1 In-Reply-To: <20220930184605.47655-1-nicolas.chautru@intel.com> References: <1655491040-183649-6-git-send-email-nicolas.chautru@intel.com> <20220930184605.47655-1-nicolas.chautru@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Adding more options in the API to expose the number of queues exposed and related priority. Signed-off-by: Nicolas Chautru Acked-by: Maxime Coquelin --- lib/bbdev/rte_bbdev.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lib/bbdev/rte_bbdev.h b/lib/bbdev/rte_bbdev.h index 5ba7a61ded..d95049d44c 100644 --- a/lib/bbdev/rte_bbdev.h +++ b/lib/bbdev/rte_bbdev.h @@ -289,6 +289,10 @@ struct rte_bbdev_driver_info { /** Maximum number of queues supported by the device */ unsigned int max_num_queues; + /** Maximum number of queues supported per operation type */ + unsigned int num_queues[RTE_BBDEV_OP_TYPE_SIZE_MAX]; + /** Priority level supported per operation type */ + unsigned int queue_priority[RTE_BBDEV_OP_TYPE_SIZE_MAX]; /** Queue size limit (queue size must also be power of 2) */ uint32_t queue_size_lim; /** Set if device off-loads operation to hardware */ -- 2.37.1