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 B1707A0093; Wed, 9 Mar 2022 01:41:41 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2D8EB4068E; Wed, 9 Mar 2022 01:41:41 +0100 (CET) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id 0B74740395 for ; Wed, 9 Mar 2022 01:41:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646786500; x=1678322500; h=from:to:cc:subject:date:message-id; bh=1XOUyZGZqOOZMrvHnLdq4V8kudG4kiQ5/6ZikYMpPT8=; b=GrRW4KNTXtZWuLmCQW+LuHMSV/pC3wiu4gYmVdZLxBjB/EO40lGFC8gZ GELnWdhjHPyzd30pIKTJPek+jCdcqs0OVdSkJw3XHnITpiW6ndaudePZy RqdGaCwEy00vhjB5A4EO5TApBotVSDSwXKGYEmf8hT0fBnKre9PcyBtsl F7qOlLlw2C0L+KAMyk+15/1TQJc22IxLHLBmXn7/mzNbVcAyXNFjz9ZMc aB5bhTmuK8e/12nqiz+TTKo/LrSXFb6FyPFm/3x6aTol5qMmgX43znOyt EwUB8uc8NsbQ3LfQuIOyK11ppMqk5YPmuKUbG/AeOODNZ1aIpXoc6ryYs A==; X-IronPort-AV: E=McAfee;i="6200,9189,10280"; a="254581975" X-IronPort-AV: E=Sophos;i="5.90,165,1643702400"; d="scan'208";a="254581975" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Mar 2022 16:41:39 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,165,1643702400"; d="scan'208";a="688116875" Received: from skx-5gnr-sc12-4.sc.intel.com ([172.25.69.210]) by fmsmga001.fm.intel.com with ESMTP; 08 Mar 2022 16:41:38 -0800 From: Nicolas Chautru To: dev@dpdk.org, gakhil@marvell.com Cc: trix@redhat.com, hemant.agrawal@nxp.com, mingshan.zhang@intel.com, Nicolas Chautru Subject: [PATCH v1 0/2] bbdev: add device info on queue topology Date: Tue, 8 Mar 2022 16:22:33 -0800 Message-Id: <1646785355-168133-1-git-send-email-nicolas.chautru@intel.com> X-Mailer: git-send-email 1.8.3.1 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 Addressing an historical concern that the device info struct only imperfectly captured what queues are available on the device (number of operation and priority). This ended up being an iterative process for application to find each queue could be configured. ie. the gap was captured as technical debt previously in comments /* This isn't ideal because it reports the maximum number of queues but * does not provide info on how many can be uplink/downlink or different * priorities */ This is now being exposed explictly based on the what the device actually supports using the existing info_get api Note: did not update the release yet notes since it will go in next release Nicolas Chautru (2): bbdev: add device info on queue topology drivers/baseband: update PMDs to expose queue per operation drivers/baseband/acc100/rte_acc100_pmd.c | 29 +++++++++++++--------- drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 8 ++++++ drivers/baseband/fpga_lte_fec/fpga_lte_fec.c | 8 ++++++ drivers/baseband/la12xx/bbdev_la12xx.c | 8 +++++- lib/bbdev/rte_bbdev.h | 4 +++ 5 files changed, 44 insertions(+), 13 deletions(-) -- 1.8.3.1