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 948DDA0032; Fri, 21 Oct 2022 11:17:00 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3EEDC42BA4; Fri, 21 Oct 2022 11:17:00 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 149B942836 for ; Fri, 21 Oct 2022 11:16:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666343818; 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=WUxwIvk6pFmRKrgxy8uSvpiWgJQodmSW3oovHKYQd5w=; b=f+5scGkLxuuKPURYHZckvzqjxbMd0g7DeMrVVtoPjb1F42DbcCrv6ia15Q6HipMxvJGLN/ YRwxk1zyuZ1IEChL1Z1rZtIG7xFEYas8x5PV9f+kLe0PI4N1+NQJSiUzSUUQyIy9S/j4Ps fJ9E2FuMizHQbIh/FIuPveGxhC3+bUg= 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-417-v_e7BHReMDiCUVTMzWms9w-1; Fri, 21 Oct 2022 05:16:57 -0400 X-MC-Unique: v_e7BHReMDiCUVTMzWms9w-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id CE743802C17; Fri, 21 Oct 2022 09:16:56 +0000 (UTC) Received: from [10.39.208.30] (unknown [10.39.208.30]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6226B1401C23; Fri, 21 Oct 2022 09:16:55 +0000 (UTC) Message-ID: <42b24e47-39c9-3ce8-e2d3-315d26634507@redhat.com> Date: Fri, 21 Oct 2022 11:16:53 +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 08/29] baseband/acc100: allocate ring/queue mem when NULL 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-9-hernan.vargas@intel.com> From: Maxime Coquelin In-Reply-To: <20221021052102.107141-9-hernan.vargas@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 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: > Allocate info ring, tail pointers and HARQ layout memory for a device > only if it hasn't already been allocated. > > Fixes: 06531464151 ("baseband/acc100: support interrupt") > Cc: stable@dpdk.org > > Signed-off-by: Hernan Vargas > --- > drivers/baseband/acc/rte_acc100_pmd.c | 30 ++++++++++++++++++--------- > 1 file changed, 20 insertions(+), 10 deletions(-) Reviewed-by: Maxime Coquelin Thanks, Maxime