From: Thomas Monjalon <thomas@monjalon.net>
To: Gagandeep Singh <g.singh@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: Akhil Goyal <gakhil@marvell.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
Tom Rix <trix@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: baseband PMD APIs
Date: Fri, 14 Oct 2022 15:06:26 +0200 [thread overview]
Message-ID: <5147172.KlZ2vcFHjT@thomas> (raw)
In-Reply-To: <BY5PR11MB44512466429F0024A39F00A4F8249@BY5PR11MB4451.namprd11.prod.outlook.com>
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 <thomas@monjalon.net>
> > Sent: Thursday, October 13, 2022 2:25 AM
> > To: Chautru, Nicolas <nicolas.chautru@intel.com>; Gagandeep Singh
> > <g.singh@nxp.com>; Hemant Agrawal <hemant.agrawal@nxp.com>
> > Cc: Akhil Goyal <gakhil@marvell.com>; david.marchand@redhat.com;
> > maxime.coquelin@redhat.com; Tom Rix <trix@redhat.com>; 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.
> >
> >
> >
>
>
prev parent reply other threads:[~2022-10-14 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CO6PR18MB448427AC621A1EDFDEBF09C7D8259@CO6PR18MB4484.namprd18.prod.outlook.com>
2022-10-13 9:25 ` Thomas Monjalon
2022-10-14 1:46 ` Chautru, Nicolas
2022-10-14 13:06 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5147172.KlZ2vcFHjT@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.com \
--cc=trix@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).