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 A8209A0545; Mon, 20 Jun 2022 18:30:49 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 52A434069C; Mon, 20 Jun 2022 18:30:49 +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 6F23640151 for ; Mon, 20 Jun 2022 18:30:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655742648; 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=Zc2jA0Dvf7Hb0ObSQcS2l+47dnPeJoC3f5LXC7PoALA=; b=BiEVo6W11pmWBXX64n9UVLPSyKSm+kvB2O4N8ihC2kVKdnhpnqdsuL/AyWL/GPodZ1ciX0 GqC+2slrcYjO7/fV4zVO/G6Pkvr2rERQNFABvs2r5l+U8bP6EN2yyAZlEcNy9W8tyNArJm 9yFqGBeFmviA1jKDd4feLK9Lm6QGr6s= 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-460-iSfsFpbFMb6sxs6SJ3LCqw-1; Mon, 20 Jun 2022 12:30:46 -0400 X-MC-Unique: iSfsFpbFMb6sxs6SJ3LCqw-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 58CC4811E80; Mon, 20 Jun 2022 16:30:46 +0000 (UTC) Received: from [10.39.208.29] (unknown [10.39.208.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A481A2166B26; Mon, 20 Jun 2022 16:30:44 +0000 (UTC) Message-ID: Date: Mon, 20 Jun 2022 18:30:43 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH v4 15/15] vdpa/mlx5: prepare virtqueue resource creation To: Li Zhang , orika@nvidia.com, viacheslavo@nvidia.com, matan@nvidia.com, shahafs@nvidia.com Cc: dev@dpdk.org, thomas@monjalon.net, rasland@nvidia.com, roniba@nvidia.com References: <20220408075606.33056-1-lizh@nvidia.com> <20220618090258.91157-1-lizh@nvidia.com> <20220618090258.91157-16-lizh@nvidia.com> From: Maxime Coquelin In-Reply-To: <20220618090258.91157-16-lizh@nvidia.com> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com 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 6/18/22 11:02, Li Zhang wrote: > Split the virtqs virt-queue resource between > the configuration threads. > Also need pre-created virt-queue resource > after virtq destruction. > This accelerates the LM process and reduces its time by 30%. > > Signed-off-by: Li Zhang > Acked-by: Matan Azrad > --- > doc/guides/rel_notes/release_22_07.rst | 1 + > drivers/vdpa/mlx5/mlx5_vdpa.c | 115 +++++++++++++++++++------ > drivers/vdpa/mlx5/mlx5_vdpa.h | 12 ++- > drivers/vdpa/mlx5/mlx5_vdpa_cthread.c | 15 +++- > drivers/vdpa/mlx5/mlx5_vdpa_virtq.c | 111 ++++++++++++++++++++---- > 5 files changed, 209 insertions(+), 45 deletions(-) > Reviewed-by: Maxime Coquelin Thanks, Maxime