From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, cristian.klein@cs.umu.se, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] Migration cancel with dead network
Date: Thu, 08 Jan 2015 13:10:18 +0100 [thread overview]
Message-ID: <54AE73AA.7060408@redhat.com> (raw)
In-Reply-To: <1420715492-5109-1-git-send-email-dgilbert@redhat.com>
On 08/01/2015 12:11, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> If the remote host, or networking dies during a migration, the socket can be
> waiting for a long timeout, and migration_cancel can't complete the cancel
> for a long time (and you can't start a new one to somewhere else).
> (Where 'long' is the TCP timeout, that's ~15 mins)
>
> This patch set uses the shutdown(2) syscall to unblock any write/sends that
> are in progress to let the migrate_cancel happen quickly.
>
> 1/3: socket shutdown - An updated patch from my postcopy world to
> add a shut_down method on QEMUFile - only
> for 'socket' (where the syscall is supported).
>
> 2/3: Handle bi-directional communication for fd migration
> - A patch from Cristian Klein to use the socket
> QEMUFile for FDs that are passed in, if the FDs
> are sockets; this is needed so that libvirt
> migrations can take advantage of the other patches.
> Again this patch (and its naming) come from the
> postcopy world.
>
> 3/3: migration_cancel: shutdown migration socket
> - A new patch that uses the shutdown in migrate_fd_cancel
>
>
> Note this does not fix the timeout if you try to migrate to an already dead host;
> the connect timeout is typically a much shorter 2 minutes anyway.
A more precise commit message for 2/3 would be nice, but the code is good.
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2015-01-08 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 11:11 [Qemu-devel] [PATCH 0/3] Migration cancel with dead network Dr. David Alan Gilbert (git)
2015-01-08 11:11 ` [Qemu-devel] [PATCH 1/3] socket shutdown Dr. David Alan Gilbert (git)
2015-01-09 6:50 ` Amit Shah
2015-01-08 11:11 ` [Qemu-devel] [PATCH 2/3] Handle bi-directional communication for fd migration Dr. David Alan Gilbert (git)
2015-01-08 11:11 ` [Qemu-devel] [PATCH 3/3] migration_cancel: shutdown migration socket Dr. David Alan Gilbert (git)
2015-01-08 11:22 ` [Qemu-devel] [PATCH 0/3] Migration cancel with dead network Daniel P. Berrange
2015-01-08 11:29 ` Dr. David Alan Gilbert
2015-01-08 11:33 ` Daniel P. Berrange
2015-01-08 12:10 ` Paolo Bonzini [this message]
2015-01-09 6:50 ` Amit Shah
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=54AE73AA.7060408@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=cristian.klein@cs.umu.se \
--cc=dgilbert@redhat.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.