From: Chris Lalancette <clalance@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH]: Add a "migrate_incoming" monitor option
Date: Fri, 01 Aug 2008 11:04:13 +0200 [thread overview]
Message-ID: <4892D18D.3060706@redhat.com> (raw)
In-Reply-To: <20080801084234.GD23993@redhat.com>
Daniel P. Berrange wrote:
> An accept trick only handles the TCP case though. I know this was Chris'
> example that we're currently using, but we intend to switch to passing
> an open file descriptor instead, and proxying the data via a secure
> channel instead of the plain tcp, or builtin SSH tunnelling.
>
> With an open FD we'll need another way - I guess just registering a
> event on POLLIN might do the trick. It seems to me that just having
> an explicit migrate incoming monitor command would be simpler than having
> to code different triggers to implement 'nowait' for each transport
> we have.
I just finished a patch to do the "nowait" for tcp as suggested by Anthony, and
it was actually far less code then I feared. It just needed a little
re-factoring of the migrate_incoming_tcp() function. I'll be posting that in a
couple of minutes. Given how this code worked out, doing a "nowait" for the fd
style is really no big deal.
Both ways (explicit monitor command and "nowait") seem to have their benefits;
the monitor command has the benefit of being more flexible, while the nowait has
the benefit of being similar to already existing Qemu commands. My preference
is for the monitor command since it seems a little more natural for a management
tool, but the nowait is clearly an option as well.
I'll also post a cleanup patch with Dan's suggestion for the monitor patch, so
both implementations will be available.
Chris Lalancette
prev parent reply other threads:[~2008-08-01 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 14:50 [PATCH]: Add a "migrate_incoming" monitor option Chris Lalancette
2008-07-31 15:11 ` Daniel P. Berrange
2008-08-01 9:09 ` Chris Lalancette
2008-07-31 17:27 ` Anthony Liguori
2008-08-01 8:42 ` Daniel P. Berrange
2008-08-01 9:04 ` Chris Lalancette [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=4892D18D.3060706@redhat.com \
--to=clalance@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
/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.