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 37B49A00C2; Fri, 14 Oct 2022 12:04:27 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 267C642D41; Fri, 14 Oct 2022 12:04:27 +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 891E742D41 for ; Fri, 14 Oct 2022 12:04:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665741865; 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=kq2aftkiCQOT3K1zjUcVfdmISLC/5oth11UATtI4+Bg=; b=LFgHWNDHqnDyKapir7Ke6dQ7FHkMRghEqZt+h6wCGp3gMCmMNXvL3ROE/PPyIfBn3PFoB3 Y6Zg0wyHmf8xPGLCQogVD9qvJpI99a1eCzS825jAY+L0rLNAGE2aYGn4pL7SBpyt6PS4s4 QmiL5ku+G5YDa43ZZBpodFL9XXU8Ngw= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-396-swApuyRtNM-vyYM9Ronv5Q-1; Fri, 14 Oct 2022 06:04:21 -0400 X-MC-Unique: swApuyRtNM-vyYM9Ronv5Q-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id BA1252932496; Fri, 14 Oct 2022 10:04:20 +0000 (UTC) Received: from [10.39.208.28] (unknown [10.39.208.28]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 81E1D2141DE5; Fri, 14 Oct 2022 10:04:19 +0000 (UTC) Message-ID: Date: Fri, 14 Oct 2022 12:04:18 +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 v3 15/30] baseband/acc100: add enqueue status To: Hernan Vargas , dev@dpdk.org, gakhil@marvell.com, trix@redhat.com Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com References: <20221012025346.204394-1-hernan.vargas@intel.com> <20221012025346.204394-16-hernan.vargas@intel.com> From: Maxime Coquelin In-Reply-To: <20221012025346.204394-16-hernan.vargas@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 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/12/22 04:53, Hernan Vargas wrote: > Add enqueue status as part of rte_bbdev_queue_data. > This is a new feature to update queue status and indicate the reason why > a previous enqueue may or may not have consumed all requested operations. > > Signed-off-by: Hernan Vargas No new line > Reviewed-by: Maxime Coquelin > --- > drivers/baseband/acc/rte_acc100_pmd.c | 56 ++++++++++++++++++++------- > 1 file changed, 42 insertions(+), 14 deletions(-) >