DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"Vargas, Hernan" <hernan.vargas@intel.com>
Subject: RE: [PATCH v5 01/12] bbdev: add FFT window width member in driver info
Date: Fri, 6 Oct 2023 20:08:35 +0000	[thread overview]
Message-ID: <BY5PR11MB4451D69274C890629CC86335F8C9A@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c4df810f-6eca-d3c1-12ed-c0c6484df295@redhat.com>

Hi Maxime, 

> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Friday, October 6, 2023 12:54 AM
> To: Chautru, Nicolas <nicolas.chautru@intel.com>; dev@dpdk.org
> Cc: hemant.agrawal@nxp.com; david.marchand@redhat.com; Vargas, Hernan
> <hernan.vargas@intel.com>
> Subject: Re: [PATCH v5 01/12] bbdev: add FFT window width member in driver
> info
> 
> 
> 
> On 10/5/23 21:48, Nicolas Chautru wrote:
> > This exposes the width of each windowing shape being configured on the
> > device. This allows to distinguish different version of the flexible
> > pointwise windowing applied to the FFT and expose this platform
> > configuration to the application.
> > This also add the total number of windows supported in the capability.
> >
> > The SRS processing chain
> > (https://doc.dpdk.org/guides/prog_guide/bbdev.html#bbdev-fft-operation
> > ) includes a pointwise multiplication by time window whose shape width
> > needs to be exposed, notably for accurate SNR estimate.
> > Using that mechanism user application can retrieve information related
> > to what has been dynamically programmed on any bbdev device supporting
> > FFT windowing operation.
> >
> > Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> > ---
> >   lib/bbdev/rte_bbdev.h    | 2 ++
> >   lib/bbdev/rte_bbdev_op.h | 2 ++
> >   2 files changed, 4 insertions(+)
> >
> > diff --git a/lib/bbdev/rte_bbdev.h b/lib/bbdev/rte_bbdev.h index
> > 2985c9f42b..d12e2e7fbc 100644
> > --- a/lib/bbdev/rte_bbdev.h
> > +++ b/lib/bbdev/rte_bbdev.h
> > @@ -349,6 +349,8 @@ struct rte_bbdev_driver_info {
> >   	const struct rte_bbdev_op_cap *capabilities;
> >   	/** Device cpu_flag requirements */
> >   	const enum rte_cpu_flag_t *cpu_flag_reqs;
> > +	/** FFT windowing width for 2048 FFT - size defined in capability. */
> > +	uint16_t *fft_window_width;
> >   };
> >
> >   /** Macro used at end of bbdev PMD list */ diff --git
> > a/lib/bbdev/rte_bbdev_op.h b/lib/bbdev/rte_bbdev_op.h index
> > 693baa8386..369ac331bf 100644
> > --- a/lib/bbdev/rte_bbdev_op.h
> > +++ b/lib/bbdev/rte_bbdev_op.h
> > @@ -905,6 +905,8 @@ struct rte_bbdev_op_cap_fft {
> >   	uint16_t num_buffers_src;
> >   	/** Num output code block buffers. */
> >   	uint16_t num_buffers_dst;
> > +	/** Number of FFT windows supported. */
> > +	uint16_t fft_windows_num;
> >   };
> >
> >   /** List of the capabilities for the MLD */
> 
> I am Ok to move forwards with this, even if I would have liked feedback from
> Hemant.
> 
> However, I think you need to add some documentation around it, as what is in
> the commit message is important and won't be visible to the end- user.

Can we extend the documentation in incremental serie? There other things that could arguably be exposed more clearly, not just this one but more generally on device enumeration which is currently limited (pretty much everything from info_get).  

> 
> Thanks,
> Maxime


  reply	other threads:[~2023-10-06 20:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 19:48 [PATCH v5 00/12] VRB2 bbdev PMD introduction Nicolas Chautru
2023-10-05 19:48 ` [PATCH v5 01/12] bbdev: add FFT window width member in driver info Nicolas Chautru
2023-10-06  7:54   ` Maxime Coquelin
2023-10-06 20:08     ` Chautru, Nicolas [this message]
2023-10-10  7:21       ` Maxime Coquelin
2023-10-05 19:48 ` [PATCH v5 02/12] baseband/acc: add FFT window width in the VRB PMD Nicolas Chautru
2023-10-06  7:55   ` Maxime Coquelin
2023-10-10  7:40     ` Maxime Coquelin
2023-10-05 19:48 ` [PATCH v5 03/12] baseband/acc: remove the 4G SO capability for VRB1 Nicolas Chautru
2023-10-05 19:48 ` [PATCH v5 04/12] baseband/acc: allocate FCW memory separately Nicolas Chautru
2023-10-05 19:49 ` [PATCH v5 05/12] baseband/acc: add support for MLD operation Nicolas Chautru
2023-10-05 19:49 ` [PATCH v5 06/12] baseband/acc: refactor to allow unified driver extension Nicolas Chautru
2023-10-06  9:32   ` Maxime Coquelin
2023-10-05 19:49 ` [PATCH v5 07/12] baseband/acc: adding VRB2 device variant Nicolas Chautru
2023-10-05 19:49 ` [PATCH v5 08/12] baseband/acc: add FEC capabilities for the VRB2 variant Nicolas Chautru
2023-10-06  9:51   ` Maxime Coquelin
2023-10-06 20:05     ` Chautru, Nicolas
2023-10-10  7:19   ` Maxime Coquelin
2023-10-05 19:49 ` [PATCH v5 09/12] baseband/acc: add FFT support to " Nicolas Chautru
2023-10-10 14:06   ` Maxime Coquelin
2023-10-05 19:49 ` [PATCH v5 10/12] baseband/acc: add MLD support in " Nicolas Chautru
2023-10-06 12:20   ` Maxime Coquelin
2023-10-05 19:49 ` [PATCH v5 11/12] baseband/acc: add support for VRB2 engine error detection Nicolas Chautru
2023-10-05 19:49 ` [PATCH v5 12/12] baseband/acc: add configure helper for VRB2 Nicolas Chautru

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=BY5PR11MB4451D69274C890629CC86335F8C9A@BY5PR11MB4451.namprd11.prod.outlook.com \
    --to=nicolas.chautru@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@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).