From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Michael R. Hines" <mrhines@digitalocean.com>
Cc: qemu-devel@nongnu.org, amit.shah@redhat.com, quintela@redhat.com,
michael@hinespot.com
Subject: Re: [Qemu-devel] [PATCH 0/3] RDMA error handling
Date: Mon, 26 Sep 2016 08:49:06 +0100 [thread overview]
Message-ID: <20160926074906.GA2029@work-vm> (raw)
In-Reply-To: <0a087a52-5495-a27e-f503-a2f04516d6bc@digitalocean.com>
* Michael R. Hines (mrhines@digitalocean.com) wrote:
> Reviewed-by: Michael R. Hines <michael@hinespot.com>
>
> (By the way, I no longer work for IBM and no longer have direct access to RDMA hardware. If someone is willing to let me login to something that does in the future, I don't mind debugging things. I just don't have any hardware of my own anymore to debug, and the last time I tried to use software RDMA it was an unpleasurable experience.)
Thanks; I did hear a rumour that SoftRoCE was going to go upstream, but
it doesn't seem to have happened yet.
Dave
>
> /*
> * Michael R. Hines
> * Senior Engineer, DigitalOcean.
> */
>
> On 09/23/2016 02:14 PM, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > lp: https://bugs.launchpad.net/qemu/+bug/1545052
> >
> > The RDMA code tends to hang if the destination dies
> > in the wrong place; this series doesn't completely fix
> > that, but in cases where the destination knows there's
> > been an error, it makes sure it tells the source and
> > that cleans up quickly.
> > If the destination just dies, then the source still hangs
> > and I still need to look at better ways to fix that.
> >
> > Dave
> >
> > Dr. David Alan Gilbert (3):
> > migration/rdma: Pass qemu_file errors across link
> > migration: Make failed migration load set file error
> > migration/rdma: Don't flag an error when we've been told about one
> >
> > migration/rdma.c | 9 ++++++++-
> > migration/savevm.c | 19 ++++++++++++-------
> > 2 files changed, 20 insertions(+), 8 deletions(-)
> >
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-09-26 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 19:14 [Qemu-devel] [PATCH 0/3] RDMA error handling Dr. David Alan Gilbert (git)
2016-09-23 19:14 ` [Qemu-devel] [PATCH 1/3] migration/rdma: Pass qemu_file errors across link Dr. David Alan Gilbert (git)
2016-09-23 19:14 ` [Qemu-devel] [PATCH 2/3] migration: Make failed migration load set file error Dr. David Alan Gilbert (git)
2016-09-23 19:14 ` [Qemu-devel] [PATCH 3/3] migration/rdma: Don't flag an error when we've been told about one Dr. David Alan Gilbert (git)
2016-09-23 19:22 ` [Qemu-devel] [PATCH 0/3] RDMA error handling Michael R. Hines
2016-09-26 7:49 ` Dr. David Alan Gilbert [this message]
2016-10-05 8:58 ` Juan Quintela
2016-10-05 9:07 ` Dr. David Alan Gilbert
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=20160926074906.GA2029@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=michael@hinespot.com \
--cc=mrhines@digitalocean.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.