All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: Juan Quintela <quintela@redhat.com>,
	Qemu Developers <qemu-devel@nongnu.org>,
	liqiang02@corp.netease.com
Subject: Re: [Qemu-devel] Question about dirty page statistics for live migration
Date: Mon, 13 Aug 2018 12:30:52 +0100	[thread overview]
Message-ID: <20180813113052.GD2488@work-vm> (raw)
In-Reply-To: <CAKXe6SKCx-=cUKMFPQQ+Wm-0==HkD9Qm6ud1Q0S0k3gi5qRKmA@mail.gmail.com>

* Li Qiang (liq3ea@gmail.com) wrote:
> 2018-08-13 17:35 GMT+08:00 Dr. David Alan Gilbert <dgilbert@redhat.com>:
> 
> > * Li Qiang (liq3ea@gmail.com) wrote:
> > > Hello Dave, Juan and all,
> > >
> > > It is useful to get the dirty page rates in guest to evaluate the guest
> > > loads
> > > so that we can make a decide to live migrate it or not. So I think we can
> > > add a on-demand qmp for showing the dirty page rates.
> > >
> > > I found someone has done this work in here:
> > > -->https://github.com/grivon/yabusame-qemu-dpt
> > > and here:
> > > https://github.com/btrplace/qemu-patch
> > >
> > > But seems not go to the upstream.
> > >
> > > I want to know your opinions about adding this qmp.
> >
> > Something like that could be good;
> 
> one easy idea we had was
> > a 'migrate null:' uri and then you would use most of the existing
> > migration code to do the measurement; you would only have to
> > add a dummy file backend,
> 
> 
> As far as I understand, here dummy file backend just means the file migrate
> to, right?

Yes; because then if you have a dummy migration destination, the rest of
the migration code will run, sync the bitmap and clear the bits, and
give you an approximation of the dirty rate.

It might still be worth having the separate code to measure it without
the overhead of the migration code; but then that's more complex - and
if you're trying to measure it to know how hard it is to migrate then
perhaps it's better to use the migration code anyway.

Dave

> Thanks,
> Li Qiang
> 
> 
> 
> > and something to stop the migration ever
> > terminating (maybe just set the downtime very low).
> >
> >
> > Dave
> >
> >
> > > Thanks,
> > > Li Qiang
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2018-08-13 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13  1:46 [Qemu-devel] Question about dirty page statistics for live migration Li Qiang
2018-08-13  9:35 ` Dr. David Alan Gilbert
2018-08-13 10:31   ` Li Qiang
2018-08-13 11:30     ` Dr. David Alan Gilbert [this message]
2018-08-14  3:15       ` Li Qiang

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=20180813113052.GD2488@work-vm \
    --to=dgilbert@redhat.com \
    --cc=liq3ea@gmail.com \
    --cc=liqiang02@corp.netease.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.