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 564CCA00C2; Fri, 14 Oct 2022 15:06:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F07DA42D89; Fri, 14 Oct 2022 15:06:39 +0200 (CEST) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by mails.dpdk.org (Postfix) with ESMTP id B627342C6E for ; Fri, 14 Oct 2022 15:06:38 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 6E1D83200945; Fri, 14 Oct 2022 09:06:33 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 14 Oct 2022 09:06:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1665752793; x= 1665839193; bh=jEJeDHadubS/vDrrRdSXRgQHAq+FcNVzn31q9Jo6A9I=; b=H 1+uleXKfrj+D5mSnW72174acbNg92mHXIlxRX1gOZ6A7PIe4Az9BG3BxFIeZdhPa SpkQYD2zFmCJ79HnWwF/M1sPAP1MZ4KXZNsdvT+8Z8eMUE1bsurpmLvQrh53flHV 03DEtRw42jv3By/6VhvY3lOpUJ9adgLgBwnvcyX2BQ2JcZC73pCGDZtTnzUx8eNv 0rs6ozb3wW4gXEJN91PQIO9whSUQ8ut3JHfSwSzFhohcRl1x/bM/4dJBA9LAY3nl +UKGuM9HQLgExm7qtPrJUDyA+4O0c13zbCFL1AAQvEm5gNvzKB3UZUCIZJyjcpTd CCuSwqCctMDlBZ8uh+sUg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1665752793; x= 1665839193; bh=jEJeDHadubS/vDrrRdSXRgQHAq+FcNVzn31q9Jo6A9I=; b=C KiyZTxHb/852dJDc1orl9IXeZu5eBEa1tNA54ZEF48uKaolK0/Y61v8RVIBSxl51 4Ccxrpy/Jci/HfVSTLtcK2Xx7gJTWLpXLuXF1XaJnKw0N+b50s97pHUU5ThJ2TKN uWyNHxolkuw5bzw/gINviqEzXz4YzwReKfIZTmiXuIMvxX9qkhl5LpzE3bdXGD5I KcVajj5ZlyRibRIWzXQDUB5n6XxMDrWvd7QZ2OUDxWVS8i1aZr5Jx7VvpL1MQZAv 3dRMSO7UIdlcb2e6wNle+425vhmDvgxtsYVpQ7S75uWb9PNoS3FF/jNRVXQ45VZg iagXblPAxt6hVdslB9UmQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeekvddgieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeejjefffffgffekfefflefgkeelteejffelledugefhheelffet heevudffudfgvdenucffohhmrghinhepughpughkrdhorhhgnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Oct 2022 09:06:31 -0400 (EDT) From: Thomas Monjalon To: Gagandeep Singh , Hemant Agrawal , "Chautru, Nicolas" Cc: Akhil Goyal , "david.marchand@redhat.com" , "maxime.coquelin@redhat.com" , Tom Rix , "dev@dpdk.org" Subject: Re: baseband PMD APIs Date: Fri, 14 Oct 2022 15:06:26 +0200 Message-ID: <5147172.KlZ2vcFHjT@thomas> In-Reply-To: References: <5703375.X9hSmTKtgW@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 14/10/2022 03:46, Chautru, Nicolas: > Hi, > There are a few options: > 1) Keep as is, but not too scalable to keep on adding PMD APIs. Still there is no plan on adding more API, so no rush. > 2) Keep API internal only (but in that case only work with static lib I believe) > 3) Take out off DPDK, but that is used by users notably OEMs and for test purpose (bbdev-test) and hence proven valuable to have everything in one place. > 4) Include under bbdev API, my concern is that this is not really meant to be used by something else than bbdev-test hence can be confusing to VRAN vendor by polluting the API. > > For the sake of discussion I have captured what 4) may look like here: https://patches.dpdk.org/project/dpdk/patch/20221014014205.38074-2-nicolas.chautru@intel.com/ > Note that the actual configuration is just a void* since that configuration structure is device specific (we cannot standardize this really, nor would there be any value to do this here). > > Note that this is definitely not blocking migration from one driver to another Thomas. That companion function is purely to help bbdev-test. If it is only for testing, it is not an issue. I just want to avoid having different API paths for major API functions. > Happy to discuss more, I don't believe we need a swift decision though. > > Thanks > Nic > > > -----Original Message----- > > From: Thomas Monjalon > > Sent: Thursday, October 13, 2022 2:25 AM > > To: Chautru, Nicolas ; Gagandeep Singh > > ; Hemant Agrawal > > Cc: Akhil Goyal ; david.marchand@redhat.com; > > maxime.coquelin@redhat.com; Tom Rix ; dev@dpdk.org > > Subject: Re: baseband PMD APIs > > > > To bbdev maintainers, > > > > Do you think we can avoid having some PMD-specific configuration? > > It looks blocking migration from a driver to another. > > How do we manage that? > > > > > > 13/10/2022 11:07, Akhil Goyal: > > > There are 6 bbdev PMDs, out of which 3 have pmd APIs - all from Intel > > > These are the PMD APIs for baseband drivers. > > > rte_acc_configure -> this is being used by 2 drivers(acc100 and acc200) > > merged in a single folder. > > > rte_fpga_5gnr_fec_configure > > > rte_fpga_lte_fec_configure > > > > > > The fpga ones have almost same syntax. > > > > > > > >