From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Andy Pei <andy.pei@intel.com>, dev@dpdk.org
Cc: chenbo.xia@intel.com, rosen.xu@intel.com, qimaix.xiao@intel.com
Subject: Re: [PATCH] vhost: fix virtio blk vDPA live migration IO drop
Date: Fri, 1 Jul 2022 15:55:27 +0200 [thread overview]
Message-ID: <a061bf27-a9b2-8ece-21cd-022521e94cbb@redhat.com> (raw)
In-Reply-To: <1655884028-193120-1-git-send-email-andy.pei@intel.com>
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
next prev parent reply other threads:[~2022-07-01 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 7:47 Andy Pei
2022-07-01 12:02 ` Maxime Coquelin
2022-07-01 13:55 ` Maxime Coquelin [this message]
2022-07-04 2:30 ` Pei, Andy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a061bf27-a9b2-8ece-21cd-022521e94cbb@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=andy.pei@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=qimaix.xiao@intel.com \
--cc=rosen.xu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).