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 0DC49A00C2; Mon, 2 Jan 2023 16:14:54 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A014C40693; Mon, 2 Jan 2023 16:14:53 +0100 (CET) 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 C664340689 for ; Mon, 2 Jan 2023 16:14:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1672672491; 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=OPZVd6nPNKQQ1Mv/PSjNzlg3GOUEbbEkmyIhEgTEnkw=; b=Ely/1Jr50bMSOOfTkfUPGBfTuNbRWvnKsQZlfhJcHJYShD2T6fPFa8iA6C1hUPydUULoEG TTIsdcdSLerYJY4FI/2l8d4xdsTUzxNa2EMXVab400gH7kSvHWN06i+H6HWczhBGmIdCZn +b8MXDnciOYPAdMyPaH93j8gyzF0h+U= 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-491-6bh3ta8vNNaoPDRvl-TUgg-1; Mon, 02 Jan 2023 10:14:48 -0500 X-MC-Unique: 6bh3ta8vNNaoPDRvl-TUgg-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A7BAF1C06900; Mon, 2 Jan 2023 15:14:47 +0000 (UTC) Received: from [10.39.208.15] (unknown [10.39.208.15]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BF5012026D4B; Mon, 2 Jan 2023 15:14:46 +0000 (UTC) Message-ID: <2068f389-ef0c-2adc-460c-ff1b96ae3ddf@redhat.com> Date: Mon, 2 Jan 2023 16:14:45 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: [PATCH] vdpa/ifc: add live migration for block device To: Andy Pei , dev@dpdk.org Cc: chenbo.xia@intel.com, xiao.w.wang@intel.com References: <1671004060-62997-1-git-send-email-andy.pei@intel.com> From: Maxime Coquelin In-Reply-To: <1671004060-62997-1-git-send-email-andy.pei@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 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 12/14/22 08:47, Andy Pei wrote: > When we use "sw-live-migration=1" in arguments, we run in SW assisted > live migration mode. > > In SW assisted live migration mode, driver will stop the device and > setup a mediated virtio ring to relay the communication between the > virtio driver and the VDPA device. > > For block devices, we have to make sure that each IO is completed. > When we terminate the above mediated virtio ring, we stop > notifying queue about new IOs, wait for all the in-flight IOs to > be completed. > > Signed-off-by: Andy Pei > --- > drivers/vdpa/ifc/ifcvf_vdpa.c | 22 ++++++++++++++++++++++ > 1 file changed, 22 insertions(+) > Reviewed-by: Maxime Coquelin Thanks, Maxime