DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Hernan Vargas <hernan.vargas@intel.com>,
	dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com
Subject: Re: [PATCH v2 08/10] baseband/acc: remove check on HARQ memory
Date: Tue, 8 Oct 2024 10:08:06 +0200	[thread overview]
Message-ID: <f611daa5-2616-45fd-8249-f40b9579c94f@redhat.com> (raw)
In-Reply-To: <20241003204912.131319-9-hernan.vargas@intel.com>



On 10/3/24 22:49, Hernan Vargas wrote:
> Automatically reset HARQ memory to prevent errors and simplify usage.
> In a way we can assume that the HARQ output operation will always
> overwrite the buffer, so we can reset this from the driver to prevent
> an error being reported when application fails to do this explicitly.


Should it be backported?

> Signed-off-by: Hernan Vargas <hernan.vargas@intel.com>
> ---
>   drivers/baseband/acc/rte_vrb_pmd.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/baseband/acc/rte_vrb_pmd.c b/drivers/baseband/acc/rte_vrb_pmd.c
> index 865a050e1b19..27c8bdca3d08 100644
> --- a/drivers/baseband/acc/rte_vrb_pmd.c
> +++ b/drivers/baseband/acc/rte_vrb_pmd.c
> @@ -2595,8 +2595,9 @@ vrb_enqueue_ldpc_dec_one_op_cb(struct acc_queue *q, struct rte_bbdev_dec_op *op,
>   	/* Hard output. */
>   	mbuf_append(h_output_head, h_output, h_out_length);
>   	if (op->ldpc_dec.harq_combined_output.length > 0) {
> -		/* Push the HARQ output into host memory. */
> +		/* Push the HARQ output into host memory overwriting existing data. */
>   		struct rte_mbuf *hq_output_head, *hq_output;
> +		op->ldpc_dec.harq_combined_output.data->data_len = 0;
>   		hq_output_head = op->ldpc_dec.harq_combined_output.data;
>   		hq_output = op->ldpc_dec.harq_combined_output.data;
>   		hq_len = op->ldpc_dec.harq_combined_output.length;

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


  reply	other threads:[~2024-10-08  8:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 20:49 [PATCH v2 00/10] acc baseband PMD fix and updates for 24.11 Hernan Vargas
2024-10-03 20:49 ` [PATCH v2 01/10] baseband/acc: fix access to deallocated mem Hernan Vargas
2024-10-03 20:49 ` [PATCH v2 02/10] baseband/acc: queue allocation refactor Hernan Vargas
2024-10-04 12:08   ` Maxime Coquelin
2024-10-04 18:19     ` Chautru, Nicolas
2024-10-07  9:31       ` Maxime Coquelin
2024-10-07 16:45         ` Chautru, Nicolas
2024-10-08  7:38           ` Maxime Coquelin
2024-10-03 20:49 ` [PATCH v2 03/10] baseband/acc: configure max queues per device Hernan Vargas
2024-10-08  7:43   ` Maxime Coquelin
2024-10-03 20:49 ` [PATCH v2 04/10] baseband/acc: future proof structure comparison Hernan Vargas
2024-10-08  7:49   ` Maxime Coquelin
2024-10-03 20:49 ` [PATCH v2 05/10] baseband/acc: enhance SW ring alignment Hernan Vargas
2024-10-08  7:51   ` Maxime Coquelin
2024-10-08 20:19     ` Chautru, Nicolas
2024-10-03 20:49 ` [PATCH v2 06/10] baseband/acc: remove soft output bypass Hernan Vargas
2024-10-08  8:00   ` Maxime Coquelin
2024-10-09 16:38     ` Chautru, Nicolas
2024-10-03 20:49 ` [PATCH v2 07/10] baseband/acc: algorithm tuning for LDPC decoder Hernan Vargas
2024-10-08  8:06   ` Maxime Coquelin
2024-10-03 20:49 ` [PATCH v2 08/10] baseband/acc: remove check on HARQ memory Hernan Vargas
2024-10-08  8:08   ` Maxime Coquelin [this message]
2024-10-08 15:38     ` Chautru, Nicolas
2024-10-03 20:49 ` [PATCH v2 09/10] baseband/acc: reset ring data valid bit Hernan Vargas
2024-10-08  8:08   ` Maxime Coquelin
2024-10-03 20:49 ` [PATCH v2 10/10] baseband/acc: cosmetic changes Hernan Vargas
2024-10-08  8:11   ` Maxime Coquelin

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=f611daa5-2616-45fd-8249-f40b9579c94f@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hernan.vargas@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=qi.z.zhang@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).