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 D247AA0032; Fri, 21 Oct 2022 11:04:47 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A837442BCB; Fri, 21 Oct 2022 11:04:47 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id E979242BCB for ; Fri, 21 Oct 2022 11:04:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666343086; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qV+FeKvoezEEaWiirN7N7VGj/t3/xEOhkslS+CImL8w=; b=CZqh6d9StbWVylclIKZ3DRUOJpRhU1b/4OdnGJCJ9NtAH5iDkfrfn4IXBg1E9DCPAj+y6e NFYjcUrQu6J1GJosVExo+/+P0Zimm2H9ikmEXkcN9b7nku5boHLlDhU/paMeS4bEmqLbGt RketKu4an79pVTOtmshnvkNFFMOwTDw= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-296-Ui61hsEBNeq9X6u3WbeH2Q-1; Fri, 21 Oct 2022 05:04:40 -0400 X-MC-Unique: Ui61hsEBNeq9X6u3WbeH2Q-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 46167185A7A3; Fri, 21 Oct 2022 09:04:40 +0000 (UTC) Received: from [10.39.208.30] (unknown [10.39.208.30]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D2C7853AA; Fri, 21 Oct 2022 09:04:38 +0000 (UTC) Message-ID: Date: Fri, 21 Oct 2022 11:04:37 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 Subject: Re: [PATCH v5 01/29] baseband/acc100: fix ring availability calculation To: Hernan Vargas , dev@dpdk.org, gakhil@marvell.com, trix@redhat.com Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com, stable@dpdk.org References: <20221021052102.107141-1-hernan.vargas@intel.com> <20221021052102.107141-2-hernan.vargas@intel.com> From: Maxime Coquelin In-Reply-To: <20221021052102.107141-2-hernan.vargas@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 On 10/21/22 07:20, Hernan Vargas wrote: > Refactor of the queue availability computation to prevent the > application to dequeue more than what may have been enqueued. > > Fixes: 5ad5060f8f7 ("baseband/acc100: add LDPC processing functions") > Cc: stable@dpdk.org > > Signed-off-by: Hernan Vargas > --- > drivers/baseband/acc/rte_acc100_pmd.c | 25 +++++++++++++------------ > 1 file changed, 13 insertions(+), 12 deletions(-) > Reviewed-by: Maxime Coquelin Thanks, Maxime