DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: dev@dpdk.org
Subject: Re: [PATCH v1 0/3] bbdev: new k0 parameter
Date: Tue, 2 Jul 2024 12:20:18 +0530	[thread overview]
Message-ID: <c7841e56-82c3-01f4-04ed-c9fb5a7af391@oss.nxp.com> (raw)
In-Reply-To: <20240701212703.417094-1-nicolas.chautru@intel.com>


On 02-07-2024 02:57, Nicolas Chautru wrote:
> Hi Maxime, Hemant,
>
> Capturing below an extension for 24.11.
> This includes bbdev api change and related change for
> test application and acc/vrb PMD.
> This provides the ability which was introduced in 3gPP
> standard to have an alternate way to compute k0 no longer
> always computed just from rv_index. When that parameter
> is set, then it is used a k0 value (starting position
> in circular index), if null the legacy computation
> from rv index (more common) is maintained.
>
> Nicolas Chautru (3):
>    bbdev: new k0 parameter for LDPC decoder operation
>    test/bbdev: add support for k0 parameter
>    baseband/acc: add support for k0 parameter
>
>   app/test-bbdev/test_bbdev_perf.c      | 7 +++++--
>   app/test-bbdev/test_bbdev_vector.c    | 4 ++++
>   app/test-bbdev/test_bbdev_vector.h    | 1 +
>   doc/guides/prog_guide/bbdev.rst       | 2 ++
>   drivers/baseband/acc/acc_common.h     | 6 ++++--
>   drivers/baseband/acc/rte_acc100_pmd.c | 2 +-
>   drivers/baseband/acc/rte_vrb_pmd.c    | 4 ++--
>   lib/bbdev/rte_bbdev_op.h              | 4 ++++
>   8 files changed, 23 insertions(+), 7 deletions(-)

looks ok to me

Series-

Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>



      parent reply	other threads:[~2024-07-02  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 21:27 Nicolas Chautru
2024-07-01 21:27 ` [PATCH v1 1/3] bbdev: new k0 parameter for LDPC decoder operation Nicolas Chautru
2024-07-01 21:27 ` [PATCH v1 2/3] test/bbdev: add support for k0 parameter Nicolas Chautru
2024-07-01 21:27 ` [PATCH v1 3/3] baseband/acc: " Nicolas Chautru
2024-07-02  6:50 ` Hemant Agrawal [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=c7841e56-82c3-01f4-04ed-c9fb5a7af391@oss.nxp.com \
    --to=hemant.agrawal@oss.nxp.com \
    --cc=dev@dpdk.org \
    /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).