From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, hernan.vargas@intel.com
Subject: Re: [PATCH v1 2/2] doc: clarify the window index usage in bbdev
Date: Thu, 2 Oct 2025 09:45:53 +0200 [thread overview]
Message-ID: <7249a88e-e4b2-418e-b75f-8a68afa1064f@redhat.com> (raw)
In-Reply-To: <20250826194324.95284-3-nicolas.chautru@intel.com>
On 8/26/25 9:43 PM, Nicolas Chautru wrote:
> Clarify the usage, range and mapping for the set of window
> indexes of each cyclic shift for the FFT processing pipeline.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> doc/guides/prog_guide/bbdev.rst | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
> index 6f1f3f65fb..064c2b1fe6 100644
> --- a/doc/guides/prog_guide/bbdev.rst
> +++ b/doc/guides/prog_guide/bbdev.rst
> @@ -296,8 +296,11 @@ Capabilities details for FFT function
>
> The total number of distinct time windows supported
> for the post-FFT point-wise multiplication is exposed as ``fft_windows_num``.
> -The ``window_index`` provided for each cyclic shift
> -in each ``rte_bbdev_op_fft`` operation is expected to be limited to that size.
> +The ``window_index`` provided for each cyclic shift in each ``rte_bbdev_op_fft`` operation is
> +expected to be within the range (0 to ``fft_windows_num`` - 1).
> +These indexes for up to 12 cyclic shifts are mapped consecutively into an array of 6 bytes
> +(ie. the first index is the first 4 most significant bits of the first byte, etc...):
> +``uint8_t window_index[RTE_BBDEV_MAX_CS_2]``.
>
> The information related to the width of each of these pre-configured window
> is also exposed using the ``fft_window_width`` array.
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2025-10-02 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 19:43 [PATCH v1 0/2] doc: bbdev clarifications Nicolas Chautru
2025-08-26 19:43 ` [PATCH v1 1/2] doc: clarify CB vs TB level device support Nicolas Chautru
2025-10-01 8:45 ` Maxime Coquelin
2025-08-26 19:43 ` [PATCH v1 2/2] doc: clarify the window index usage in bbdev Nicolas Chautru
2025-10-02 7:45 ` Maxime Coquelin [this message]
2025-08-29 5:08 ` [PATCH v1 0/2] doc: bbdev clarifications Hemant Agrawal
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=7249a88e-e4b2-418e-b75f-8a68afa1064f@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=nicolas.chautru@intel.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).