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 76A08A00C3; Thu, 16 Jun 2022 09:24:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5FBD34281E; Thu, 16 Jun 2022 09:24:23 +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 551214114F for ; Thu, 16 Jun 2022 09:24:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655364261; 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=6Qe8mzu+BncqFhqADHDtDSBI5147kM94TUiKqIwYw/o=; b=gQuMyRWnIej0NpQiprzO0oC+0kUdIlQpmzG/rGIWpEyHI83c9NE3rafwH8HIkSynVLSvRA YkJCHAwAOSNmt1pZio356idHLYBj8MCRPWSYIPL6ZkVbgQH5O2R1TgY4DBJfd5BggVQnsy du+Yql8Q2Abl1kxmA0UVg05KZdCESbQ= 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-592-19OJb7EwPU-QmYq1E2APiA-1; Thu, 16 Jun 2022 03:24:20 -0400 X-MC-Unique: 19OJb7EwPU-QmYq1E2APiA-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id F35873C0CD4C; Thu, 16 Jun 2022 07:24:19 +0000 (UTC) Received: from [10.39.208.29] (unknown [10.39.208.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6DBF5415F5E; Thu, 16 Jun 2022 07:24:18 +0000 (UTC) Message-ID: Date: Thu, 16 Jun 2022 09:24:16 +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 v2 00/15] mlx5/vdpa: optimize live migration time 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> <20220616023012.16013-1-lizh@nvidia.com> From: Maxime Coquelin In-Reply-To: <20220616023012.16013-1-lizh@nvidia.com> X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 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 Hi Li, On 6/16/22 04:29, Li Zhang wrote: > Allow the driver to use internal threads to > obtain fast configuration. > All the threads will be open on the same core of > the event completion queue scheduling thread. > > Add max_conf_threads parameter to configure > the maximum number of internal threads in addition to > the caller thread (8 is suggested). > These internal threads to pipeline handle VDPA tasks > in system and shared with all VDPA devices. > Default is 0, don't use internal threads for configuration. > > Depends-on: series=21868 ("vdpa/mlx5: improve device shutdown time") > http://patchwork.dpdk.org/project/dpdk/list/?series=21868 > > RFC ("Add vDPA multi-threads optiomization") > https://patchwork.dpdk.org/project/dpdk/cover/20220408075606.33056-1-lizh@nvidia.com/ I just notice there was a RFC that was sent on time because I was not cc'ed. I thought V1, which arrived on June 6th was targetting v22.11. Given how late we are in the schedule for v22.07, this series will be postponed to v22.11. Regards, Maxime > V2: > * Drop eal device removal patch in series. > * Add release note in release_22_07.rst. > > Li Zhang (12): > vdpa/mlx5: fix usage of capability for max number of virtqs > common/mlx5: extend virtq modifiable fields > vdpa/mlx5: pre-create virtq in the prob > vdpa/mlx5: optimize datapath-control synchronization > vdpa/mlx5: add multi-thread management for configuration > vdpa/mlx5: add task ring for MT management > vdpa/mlx5: add MT task for VM memory registration > vdpa/mlx5: add virtq creation task for MT management > vdpa/mlx5: add virtq LM log task > vdpa/mlx5: add device close task > vdpa/mlx5: add virtq sub-resources creation > vdpa/mlx5: prepare virtqueue resource creation > > Yajun Wu (3): > vdpa/mlx5: support pre create virtq resource > common/mlx5: add DevX API to move QP to reset state > vdpa/mlx5: support event qp reuse > > doc/guides/rel_notes/release_22_07.rst | 5 + > doc/guides/vdpadevs/mlx5.rst | 25 + > drivers/common/mlx5/mlx5_devx_cmds.c | 77 ++- > drivers/common/mlx5/mlx5_devx_cmds.h | 6 +- > drivers/common/mlx5/mlx5_prm.h | 30 +- > drivers/vdpa/mlx5/meson.build | 1 + > drivers/vdpa/mlx5/mlx5_vdpa.c | 270 ++++++++-- > drivers/vdpa/mlx5/mlx5_vdpa.h | 152 +++++- > drivers/vdpa/mlx5/mlx5_vdpa_cthread.c | 360 ++++++++++++++ > drivers/vdpa/mlx5/mlx5_vdpa_event.c | 160 ++++-- > drivers/vdpa/mlx5/mlx5_vdpa_lm.c | 128 ++++- > drivers/vdpa/mlx5/mlx5_vdpa_mem.c | 270 ++++++---- > drivers/vdpa/mlx5/mlx5_vdpa_steer.c | 22 +- > drivers/vdpa/mlx5/mlx5_vdpa_virtq.c | 654 ++++++++++++++++++------- > 14 files changed, 1776 insertions(+), 384 deletions(-) > create mode 100644 drivers/vdpa/mlx5/mlx5_vdpa_cthread.c >