From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk/vhost-user and VM migration
Date: Fri, 16 Oct 2015 15:37:38 +0800 [thread overview]
Message-ID: <20151016073738.GK3115@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20151014000508-mutt-send-email-mst@redhat.com>
On Wed, Oct 14, 2015 at 12:16:29AM +0300, Michael S. Tsirkin wrote:
> Hello!
> I am currently looking at how using dpdk on host, accessing VM memory
> using the vhost-user interface, interacts with VM migration.
>
> The issue is that any changes made to VM memory need to be tracked so
> that updates can be sent from migration source to destination.
>
> At the moment, there's a proposal of an interface extension to
> vhost-user which adds ability to do this tracking through shared memory.
> dpdk would then be responsible for tracking these updates using atomic
> operations to set bits (per page written) in a memory bitmap.
>
> This only needs to happen during migration, at other times there could
> be a jump to skip this logging.
>
> Is this a reasonable approach?
Hi Michael,
As I stated in another email, adding dpdk/vhost-user vm migration
support is my second TODO. However, I barely know anything about
vm migration so far, that I can't tell now.
I will re-visit this question when I finished my first item and
after some more investigation.
--yliu
> Would performance degradation during
> migration associated with atomics affect the performance to a level
> where it's no longer useful? Pls note these logs aren't latency
> sensitive, so can be done on a separate core, and can be batched.
>
>
> One alternative I'm considering is extending linux kernel so it can do
> this tracking automatically, by marking pages read-only, detecting a
> pagefault and logging the write, then making the pages writeable. This
> would mean higher worst-case overhead (pagefaults are expensive) but
> lower average one (not extra code after the first fault). Not sure how
> feasible this is yet, this would be harder to implement and it will only
> be apply to newer host kernels.
>
> Any feedback would be appreciated.
>
> --
> MST
next prev parent reply other threads:[~2015-10-16 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:16 Michael S. Tsirkin
2015-10-16 7:37 ` Yuanhan Liu [this message]
2015-10-28 9:52 ` Amnon Ilan
2015-10-28 12:30 ` Yuanhan Liu
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=20151016073738.GK3115@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).