All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: Benoit Hudzia <benoit.hudzia@gmail.com>
Cc: Avi Kivity <avi@redhat.com>,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	Andrea Arcangeli <aarcange@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	t.hirofuchi@aist.go.jp, satoshi.itoh@aist.go.jp
Subject: Re: [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy
Date: Fri, 13 Jan 2012 10:31:53 +0900	[thread overview]
Message-ID: <4F0F8989.8040907@oss.ntt.co.jp> (raw)
In-Reply-To: <CAEWUdFXdGaumPC+6YxpsFofPOyuzNGa1xc5E2Y1BFkSKYyTtJQ@mail.gmail.com>

(2012/01/13 10:09), Benoit Hudzia wrote:
> Hi,
>
> Sorry to jump to hijack the thread  like that , however i would like
> to just to inform you  that we recently achieve a milestone out of the
> research project I'm leading. We enhanced KVM in order to deliver
> post copy live migration using RDMA at kernel level.
>
> Few point on the architecture of the system :
>
> * RDMA communication engine in kernel ( you can use soft iwarp or soft
> ROCE if you don't have hardware acceleration, however we also support
> standard RDMA enabled NIC) .
> * Naturally Page are transferred with Zerop copy protocol
> * Leverage the async page fault system.
> * Pre paging / faulting
> * No context switch as everything is handled within kernel and using
> the page fault system.
> * Hybrid migration ( pre + post copy) available
> * Rely on an independent Kernel Module
> * No modification to the KVM kernel Module
> * Minimal Modification to the Qemu-Kvm code
> * We plan to add the page prioritization algo in order to optimise the
> pre paging algo and background transfer
>
>
> You can learn a little bit more and see a demo here:
> http://tinyurl.com/8xa2bgl
> I hope to be able to provide more detail on the design soon. As well
> as more concrete demo of the system ( live migration of VM running
> large  enterprise apps such as ERP or In memory DB)
>
> Note: this is just a step stone as the post copy live migration mainly
> enable us to validate the architecture design and  code.

Do you have any plan to send the patch series of your implementation?

	Takuya

WARNING: multiple messages have this Message-ID (diff)
From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: Benoit Hudzia <benoit.hudzia@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	kvm@vger.kernel.org, satoshi.itoh@aist.go.jp,
	t.hirofuchi@aist.go.jp, qemu-devel@nongnu.org,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy
Date: Fri, 13 Jan 2012 10:31:53 +0900	[thread overview]
Message-ID: <4F0F8989.8040907@oss.ntt.co.jp> (raw)
In-Reply-To: <CAEWUdFXdGaumPC+6YxpsFofPOyuzNGa1xc5E2Y1BFkSKYyTtJQ@mail.gmail.com>

(2012/01/13 10:09), Benoit Hudzia wrote:
> Hi,
>
> Sorry to jump to hijack the thread  like that , however i would like
> to just to inform you  that we recently achieve a milestone out of the
> research project I'm leading. We enhanced KVM in order to deliver
> post copy live migration using RDMA at kernel level.
>
> Few point on the architecture of the system :
>
> * RDMA communication engine in kernel ( you can use soft iwarp or soft
> ROCE if you don't have hardware acceleration, however we also support
> standard RDMA enabled NIC) .
> * Naturally Page are transferred with Zerop copy protocol
> * Leverage the async page fault system.
> * Pre paging / faulting
> * No context switch as everything is handled within kernel and using
> the page fault system.
> * Hybrid migration ( pre + post copy) available
> * Rely on an independent Kernel Module
> * No modification to the KVM kernel Module
> * Minimal Modification to the Qemu-Kvm code
> * We plan to add the page prioritization algo in order to optimise the
> pre paging algo and background transfer
>
>
> You can learn a little bit more and see a demo here:
> http://tinyurl.com/8xa2bgl
> I hope to be able to provide more detail on the design soon. As well
> as more concrete demo of the system ( live migration of VM running
> large  enterprise apps such as ERP or In memory DB)
>
> Note: this is just a step stone as the post copy live migration mainly
> enable us to validate the architecture design and  code.

Do you have any plan to send the patch series of your implementation?

	Takuya

  reply	other threads:[~2012-01-13  1:30 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29  1:26 [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy Isaku Yamahata
2011-12-29  1:26 ` [Qemu-devel] " Isaku Yamahata
2011-12-29  1:26 ` [PATCH 1/2] export necessary symbols Isaku Yamahata
2011-12-29  1:26   ` [Qemu-devel] " Isaku Yamahata
2011-12-29  1:26 ` [PATCH 2/2] umem: chardevice for kvm postcopy Isaku Yamahata
2011-12-29  1:26   ` [Qemu-devel] " Isaku Yamahata
2011-12-29 11:17   ` Avi Kivity
2011-12-29 11:17     ` [Qemu-devel] " Avi Kivity
2011-12-29 12:22     ` Isaku Yamahata
2011-12-29 12:22       ` [Qemu-devel] " Isaku Yamahata
2011-12-29 12:47       ` Avi Kivity
2011-12-29 12:47         ` [Qemu-devel] " Avi Kivity
2012-01-05  4:08   ` 回复: " thfbjyddx
2012-01-05  4:08     ` [Qemu-devel] " thfbjyddx
2012-01-05 10:48     ` 回??: " Isaku Yamahata
2012-01-05 10:48       ` [Qemu-devel] " Isaku Yamahata
2012-01-05 11:10       ` Tommy
2012-01-05 11:10         ` [Qemu-devel] " Tommy
2012-01-05 12:18         ` Isaku Yamahata
2012-01-05 12:18           ` [Qemu-devel] " Isaku Yamahata
2012-01-05 15:02           ` Tommy Tang
2012-01-05 15:02             ` [Qemu-devel] " Tommy Tang
     [not found]           ` <4F05BB68.9050302@hotmail.com>
2012-01-05 15:05             ` Tommy Tang
2012-01-05 15:05               ` [Qemu-devel] " Tommy Tang
2012-01-06  7:02           ` thfbjyddx
2012-01-06  7:02             ` [Qemu-devel] " thfbjyddx
2012-01-06 17:13             ` 回??: [PATCH 2/2] umem: chardevice for kvm?postcopy Isaku Yamahata
2012-01-06 17:13               ` [Qemu-devel] " Isaku Yamahata
2011-12-29  1:31 ` [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy Isaku Yamahata
2011-12-29  1:31   ` [Qemu-devel] " Isaku Yamahata
2011-12-29 11:24 ` Avi Kivity
2011-12-29 11:24   ` [Qemu-devel] " Avi Kivity
2011-12-29 12:39   ` Isaku Yamahata
2011-12-29 12:39     ` [Qemu-devel] " Isaku Yamahata
2011-12-29 12:55     ` Avi Kivity
2011-12-29 12:55       ` [Qemu-devel] " Avi Kivity
2011-12-29 13:49       ` Isaku Yamahata
2011-12-29 13:49         ` [Qemu-devel] " Isaku Yamahata
2011-12-29 13:52         ` Avi Kivity
2011-12-29 13:52           ` [Qemu-devel] " Avi Kivity
2011-12-29 14:18           ` Isaku Yamahata
2011-12-29 14:18             ` [Qemu-devel] " Isaku Yamahata
2011-12-29 14:35             ` Avi Kivity
2011-12-29 14:35               ` [Qemu-devel] " Avi Kivity
2011-12-29 14:49               ` Isaku Yamahata
2011-12-29 14:49                 ` [Qemu-devel] " Isaku Yamahata
2011-12-29 14:55                 ` Avi Kivity
2011-12-29 14:55                   ` [Qemu-devel] " Avi Kivity
2011-12-29 15:53                   ` Isaku Yamahata
2011-12-29 15:53                     ` [Qemu-devel] " Isaku Yamahata
2011-12-29 16:00                     ` Avi Kivity
2011-12-29 16:00                       ` [Qemu-devel] " Avi Kivity
2011-12-29 16:01                       ` Avi Kivity
2011-12-29 16:01                         ` [Qemu-devel] " Avi Kivity
2012-01-02 17:05                         ` Andrea Arcangeli
2012-01-02 17:05                           ` [Qemu-devel] " Andrea Arcangeli
2012-01-02 17:55                           ` Paolo Bonzini
2012-01-02 17:55                             ` [Qemu-devel] " Paolo Bonzini
2012-01-03 14:25                             ` Andrea Arcangeli
2012-01-03 14:25                               ` [Qemu-devel] " Andrea Arcangeli
2012-01-12 13:57                               ` Avi Kivity
2012-01-12 13:57                                 ` [Qemu-devel] " Avi Kivity
2012-01-13  2:06                                 ` Andrea Arcangeli
2012-01-13  2:06                                   ` [Qemu-devel] " Andrea Arcangeli
2012-01-04  3:03                           ` Isaku Yamahata
2012-01-04  3:03                             ` [Qemu-devel] " Isaku Yamahata
2012-01-12 13:59                             ` Avi Kivity
2012-01-12 13:59                               ` [Qemu-devel] " Avi Kivity
2012-01-13  1:09                               ` Benoit Hudzia
2012-01-13  1:09                                 ` [Qemu-devel] " Benoit Hudzia
2012-01-13  1:31                                 ` Takuya Yoshikawa [this message]
2012-01-13  1:31                                   ` Takuya Yoshikawa
2012-01-13  9:40                                   ` Benoit Hudzia
2012-01-13  9:40                                     ` [Qemu-devel] " Benoit Hudzia
2012-01-13  2:03                                 ` Isaku Yamahata
2012-01-13  2:03                                   ` [Qemu-devel] " Isaku Yamahata
2012-01-13  2:15                                   ` Isaku Yamahata
2012-01-13  2:15                                     ` [Qemu-devel] " Isaku Yamahata
2012-01-13  9:55                                     ` Benoit Hudzia
2012-01-13  9:55                                       ` [Qemu-devel] " Benoit Hudzia
2012-01-13  9:48                                   ` Benoit Hudzia
2012-01-13  9:48                                     ` [Qemu-devel] " Benoit Hudzia
2012-01-13  2:09                               ` Andrea Arcangeli
2012-01-13  2:09                                 ` [Qemu-devel] " Andrea Arcangeli

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=4F0F8989.8040907@oss.ntt.co.jp \
    --to=yoshikawa.takuya@oss.ntt.co.jp \
    --cc=aarcange@redhat.com \
    --cc=avi@redhat.com \
    --cc=benoit.hudzia@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=satoshi.itoh@aist.go.jp \
    --cc=t.hirofuchi@aist.go.jp \
    --cc=yamahata@valinux.co.jp \
    /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.