qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Sukrit Bhatnagar <skrtbhtngr@gmail.com>, qemu-devel@nongnu.org
Cc: Yuval Shaia <yuval.shaia@oracle.com>
Subject: Re: [Qemu-devel] [PATCH v1 0/2] Add live migration support in the PVRDMA device
Date: Sat, 31 Aug 2019 22:37:44 +0300	[thread overview]
Message-ID: <6714c8f2-a139-94a1-4e9b-2e25e0c97b27@gmail.com> (raw)
In-Reply-To: <20190828142328.24561-1-skrtbhtngr@gmail.com>

Hi Sukrit,

On 8/28/19 5:23 PM, Sukrit Bhatnagar wrote:
> This series enables the migration of various GIDs used by the device.
> This is in addition to the successful migration of PCI and MSIX states
> as well as various DMA addresses and ring page information.
>      
> We have a setup having two hosts and two VMs running atop them.
> Migrations are performed over the local network.
>
> We also have performed various ping-pong tests (ibv_rc_pingpong) in the
> guest(s) after adding GID migration support and this is the current status:
> - ping-pong to localhost succeeds, when performed before starting the
>    migration and after the completion of migration.
> - ping-pong to a peer succeeds, both before and after migration as above,
>    provided that both VMs are running on/migrated to the same host.
>    So, if two VMs were started on two different hosts, and one of them
>    was migrated to the other host, the ping-pong was successful.
>    Similarly, if two VMs are migrated to the same host, then after migration,
>    the ping-pong was successful.
> - ping-pong to a peer on the remote host is not working as of now.
>      
> Our next goal is to achieve successful migration with live traffic.
>      

Nice work!
I am sorry for the GSOC program interruption and congrats
on your decision to continue the project!

Thanks,
Marcel

> This is the same as the RFC v3 series posted earlier:
> https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg04752.html
> https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg04753.html
> https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg04754.html
>
>
> Sukrit Bhatnagar (2):
>    hw/pvrdma: make DSR mapping idempotent in load_dsr()
>    hw/pvrdma: add live migration support
>
>   hw/rdma/vmw/pvrdma_main.c | 94 +++++++++++++++++++++++++++++++++++----
>   1 file changed, 86 insertions(+), 8 deletions(-)
>



      parent reply	other threads:[~2019-08-31 19:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 14:23 [Qemu-devel] [PATCH v1 0/2] Add live migration support in the PVRDMA device Sukrit Bhatnagar
2019-08-28 14:23 ` [Qemu-devel] [PATCH v1 1/2] hw/pvrdma: make DSR mapping idempotent in load_dsr() Sukrit Bhatnagar
2019-08-29 12:57   ` Yuval Shaia
2019-08-31 19:39   ` Marcel Apfelbaum
2019-08-28 14:23 ` [Qemu-devel] [PATCH v1 2/2] hw/pvrdma: add live migration support Sukrit Bhatnagar
2019-08-29 12:53   ` Yuval Shaia
2019-09-03 21:33     ` Sukrit Bhatnagar
2019-09-04  5:04       ` Yuval Shaia
2019-08-29 12:56   ` Yuval Shaia
2019-08-31 19:45   ` Marcel Apfelbaum
2019-09-01  9:35     ` Yuval Shaia
2019-09-03 11:05     ` Sukrit Bhatnagar
2019-08-29 12:00 ` [Qemu-devel] [PATCH v1 0/2] Add live migration support in the PVRDMA device Yuval Shaia
2019-08-31 19:37 ` Marcel Apfelbaum [this message]

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=6714c8f2-a139-94a1-4e9b-2e25e0c97b27@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=skrtbhtngr@gmail.com \
    --cc=yuval.shaia@oracle.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).