All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Yaodong Yang <yyang@cse.unl.edu>,
	qemu-discuss@nongnu.org, qemu-devel@nongnu.org
Cc: Yaodong Yang <yaodong.yangy@gmail.com>
Subject: Re: [Qemu-devel] QEMU live block-migration
Date: Mon, 08 Jul 2013 10:32:04 -0500	[thread overview]
Message-ID: <20130708153204.24640.79175@loki> (raw)
In-Reply-To: <CAJ3ZQbMCx71y-5HNYqMAVwOtXMgMBdrqDqRJVCL0miArxtVDJA@mail.gmail.com>

Quoting Yaodong Yang (2013-07-07 09:55:06)
> Hello everyone,
>    I have a short question about the implementation of QEMU. When the qemu
>    perform the live block migration using "migrate -b tcp:...." command. Does
>    a new thread for migration created or not? I went through the code, only
>    find that this activity is triggered in the main loop (main_loop_wait(int

An outgoing non-blocking connection is triggered by
tcp_start_outgoing_migration, once the connection is completed the
tcp_wait_for_connect() callback is executed by the main loop.

>    nonblocking) function). I want to know is there a new dedicated thread
>    created for this migration task or not? If so, where in the code the new
>    thread created.

Within that callback there's a call to migrate_fd_connect(), which is where the
migration thread is created.

Incoming migration is still handled by the main loop's thread

>    Thanks!
>    Yaodong
>    --
>    Yaodong Yang
>    Computer Science and Engineering Department
>    University of Nebraska--Lincoln, 
>    Lincoln, NE, U.S.A.

  reply	other threads:[~2013-07-08 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-07 14:55 [Qemu-devel] QEMU live block-migration Yaodong Yang
2013-07-08 15:32 ` Michael Roth [this message]
2013-07-08 15:57   ` Yaodong Yang
2013-07-08 17:18     ` Michael Roth
2013-07-08 17:29       ` Yaodong Yang
2013-07-08 18:02         ` Yaodong Yang

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=20130708153204.24640.79175@loki \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=yaodong.yangy@gmail.com \
    --cc=yyang@cse.unl.edu \
    /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.