From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C5FE945AA4; Thu, 3 Oct 2024 22:54:41 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5E1F5406BA; Thu, 3 Oct 2024 22:54:11 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.18]) by mails.dpdk.org (Postfix) with ESMTP id F236640273 for ; Thu, 3 Oct 2024 22:54:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1727988841; x=1759524841; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=ihwcSOAEcSpQDu3NbfYJz7i1kJp6jlHDJTRLjx7Tvg8=; b=MIWMyBRYnY52LchhL6h9wUxLR66ifEkpE+wAgrb7qPJyb1g3oA+pBsx/ DUCCiEzPzHb5H0KfX1VxSCPgzRNxFUsnb937elanBKGYOUIan3+0B0yFO wiacO6VTb1YFnjHeFvdZZSNnklZ7Udc+yavAkYsM+smm2EMkfZnKs77rV nvReM8Ir9JoobIpscbL2MwV1IshagYhKGZRYAaTSk+vPo6poNP0VD2ffm fVTjfgj06K9a3jjFLv0Cx9OshYPJ8GyLn0FipIV9QNJmIKOA1ZleIvK4S 5jXF3EH/RgHmEmyV3ZG+CKdi4CJMpVfO/kMtUAuP1ev4PXoHk1bJsyBOp A==; X-CSE-ConnectionGUID: pAQcsk/kQSiI3lMbWYLv/w== X-CSE-MsgGUID: JLgzS3mTQSW+tm3sm9akag== X-IronPort-AV: E=McAfee;i="6700,10204,11214"; a="26672694" X-IronPort-AV: E=Sophos;i="6.11,175,1725346800"; d="scan'208";a="26672694" Received: from fmviesa009.fm.intel.com ([10.60.135.149]) by fmvoesa112.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Oct 2024 13:54:00 -0700 X-CSE-ConnectionGUID: qjDPXhf7QMu04saHPmntYg== X-CSE-MsgGUID: HIFeQ9Y5Q0udzR7j/qRm/w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.11,175,1725346800"; d="scan'208";a="74473468" Received: from unknown (HELO csl-npg-qt0.la.intel.com) ([10.233.181.103]) by fmviesa009.fm.intel.com with ESMTP; 03 Oct 2024 13:54:00 -0700 From: Hernan Vargas To: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com, maxime.coquelin@redhat.com Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com, Hernan Vargas Subject: [PATCH v2 08/10] baseband/acc: remove check on HARQ memory Date: Thu, 3 Oct 2024 13:49:10 -0700 Message-Id: <20241003204912.131319-9-hernan.vargas@intel.com> X-Mailer: git-send-email 2.37.1 In-Reply-To: <20241003204912.131319-1-hernan.vargas@intel.com> References: <20241003204912.131319-1-hernan.vargas@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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. Signed-off-by: Hernan Vargas --- 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; -- 2.37.1