diff mbox series

vhost: fix virtio blk vDPA live migration IO drop

Message ID 1655884028-193120-1-git-send-email-andy.pei@intel.com (mailing list archive)
State Awaiting Upstream
Delegated to: Maxime Coquelin
Headers show
Series vhost: fix virtio blk vDPA live migration IO drop | expand

Checks

Context Check Description
ci/iol-abi-testing success Testing PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/github-robot: build success github build: passed
ci/iol-x86_64-compile-testing success Testing PASS
ci/iol-x86_64-unit-testing success Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-intel-Performance success Performance Testing PASS
ci/intel-Testing success Testing PASS
ci/iol-aarch64-unit-testing success Testing PASS
ci/iol-aarch64-compile-testing success Testing PASS
ci/Intel-compilation success Compilation OK
ci/checkpatch success coding style OK

Commit Message

Pei, Andy June 22, 2022, 7:47 a.m. UTC
In the virtio blk vDPA live migration use case, before the live
migration process, QEMU will set call fd to vDPA back-end. QEMU
and vDPA back-end stand by until live migration starts.
During live migration process, QEMU sets kick fd and a new call
fd. However, after the kick fd is set to the vDPA back-end, the
vDPA back-end configures device and data path starts. The new
call fd will cause some kind of "re-configuration", this kind
of "re-configuration" cause IO drop.
After this patch, vDPA back-end configures device after kick fd
and call fd are well set and make sure no IO drops.
This patch only impact virtio blk vDPA device and does not impact
net device.

Fixes: 7015b6577178 ("vdpa/ifc: add block device SW live-migration")

Signed-off-by: Andy Pei <andy.pei@intel.com>
---
 lib/vhost/vhost_user.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

Comments

Maxime Coquelin July 1, 2022, 12:02 p.m. UTC | #1
On 6/22/22 09:47, Andy Pei wrote:
> In the virtio blk vDPA live migration use case, before the live
> migration process, QEMU will set call fd to vDPA back-end. QEMU
> and vDPA back-end stand by until live migration starts.
> During live migration process, QEMU sets kick fd and a new call
> fd. However, after the kick fd is set to the vDPA back-end, the
> vDPA back-end configures device and data path starts. The new
> call fd will cause some kind of "re-configuration", this kind
> of "re-configuration" cause IO drop.
> After this patch, vDPA back-end configures device after kick fd
> and call fd are well set and make sure no IO drops.
> This patch only impact virtio blk vDPA device and does not impact
> net device.
> 
> Fixes: 7015b6577178 ("vdpa/ifc: add block device SW live-migration")
> 
> Signed-off-by: Andy Pei <andy.pei@intel.com>
> ---
>   lib/vhost/vhost_user.c | 15 +++++++++++++++
>   1 file changed, 15 insertions(+)
> 

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime
Maxime Coquelin July 1, 2022, 1:55 p.m. UTC | #2
On 6/22/22 09:47, Andy Pei wrote:
> In the virtio blk vDPA live migration use case, before the live
> migration process, QEMU will set call fd to vDPA back-end. QEMU
> and vDPA back-end stand by until live migration starts.
> During live migration process, QEMU sets kick fd and a new call
> fd. However, after the kick fd is set to the vDPA back-end, the
> vDPA back-end configures device and data path starts. The new
> call fd will cause some kind of "re-configuration", this kind
> of "re-configuration" cause IO drop.
> After this patch, vDPA back-end configures device after kick fd
> and call fd are well set and make sure no IO drops.
> This patch only impact virtio blk vDPA device and does not impact
> net device.
> 
> Fixes: 7015b6577178 ("vdpa/ifc: add block device SW live-migration")
> 
> Signed-off-by: Andy Pei <andy.pei@intel.com>
> ---
>   lib/vhost/vhost_user.c | 15 +++++++++++++++
>   1 file changed, 15 insertions(+)
> 

Applied to dpdk-next-virtio/main.

Thanks,
Maxime
Pei, Andy July 4, 2022, 2:30 a.m. UTC | #3
HI Maxime,

Thanks.

> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Friday, July 1, 2022 9:55 PM
> To: Pei, Andy <andy.pei@intel.com>; dev@dpdk.org
> Cc: Xia, Chenbo <chenbo.xia@intel.com>; Xu, Rosen <rosen.xu@intel.com>;
> Xiao, QimaiX <qimaix.xiao@intel.com>
> Subject: Re: [PATCH] vhost: fix virtio blk vDPA live migration IO drop
> 
> 
> 
> On 6/22/22 09:47, Andy Pei wrote:
> > In the virtio blk vDPA live migration use case, before the live
> > migration process, QEMU will set call fd to vDPA back-end. QEMU and
> > vDPA back-end stand by until live migration starts.
> > During live migration process, QEMU sets kick fd and a new call fd.
> > However, after the kick fd is set to the vDPA back-end, the vDPA
> > back-end configures device and data path starts. The new call fd will
> > cause some kind of "re-configuration", this kind of "re-configuration"
> > cause IO drop.
> > After this patch, vDPA back-end configures device after kick fd and
> > call fd are well set and make sure no IO drops.
> > This patch only impact virtio blk vDPA device and does not impact net
> > device.
> >
> > Fixes: 7015b6577178 ("vdpa/ifc: add block device SW live-migration")
> >
> > Signed-off-by: Andy Pei <andy.pei@intel.com>
> > ---
> >   lib/vhost/vhost_user.c | 15 +++++++++++++++
> >   1 file changed, 15 insertions(+)
> >
> 
> Applied to dpdk-next-virtio/main.
> 
> Thanks,
> Maxime
diff mbox series

Patch

diff --git a/lib/vhost/vhost_user.c b/lib/vhost/vhost_user.c
index 2b9a3b6..cc03f67 100644
--- a/lib/vhost/vhost_user.c
+++ b/lib/vhost/vhost_user.c
@@ -2946,6 +2946,7 @@  static int is_vring_iotlb(struct virtio_net *dev,
 	int ret;
 	int unlock_required = 0;
 	bool handled;
+	uint32_t vdpa_type = 0;
 	uint32_t request;
 	uint32_t i;
 
@@ -3152,6 +3153,20 @@  static int is_vring_iotlb(struct virtio_net *dev,
 	if (!vdpa_dev)
 		goto out;
 
+	if (vdpa_dev->ops->get_dev_type) {
+		ret = vdpa_dev->ops->get_dev_type(vdpa_dev, &vdpa_type);
+		if (ret) {
+			VHOST_LOG_CONFIG(ERR, "failed to get vdpa dev type.\n");
+			ret = -1;
+			goto out;
+		}
+	} else {
+		vdpa_type = RTE_VHOST_VDPA_DEVICE_TYPE_NET;
+	}
+	if (vdpa_type == RTE_VHOST_VDPA_DEVICE_TYPE_BLK
+		&& request != VHOST_USER_SET_VRING_CALL)
+		goto out;
+
 	if (!(dev->flags & VIRTIO_DEV_VDPA_CONFIGURED)) {
 		if (vdpa_dev->ops->dev_conf(dev->vid))
 			VHOST_LOG_CONFIG(ERR, "(%s) failed to configure vDPA device\n",