qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] augment info migrate with page status
Date: Thu, 21 May 2009 11:20:15 -0300	[thread overview]
Message-ID: <20090521142015.GB24584@poweredge.glommer> (raw)
In-Reply-To: <20090521140504.GA10055@redhat.com>

On Thu, May 21, 2009 at 03:05:04PM +0100, Daniel P. Berrange wrote:
> On Wed, May 20, 2009 at 07:20:05PM -0400, Glauber Costa wrote:
> > This patch augments info migrate output with status about:
> > * pages remaining
> > * pages transferred
> 
> Could you add 'pages total' and/or possibly 'page size', so apps 
> using this can more easily do calculations, without having to worry
> about hardcoding page sizes for each architecture they deal with. 
That can be done.

> 
> Oh, what happens if the guest is backed by huge pages ? Does the
> 'pages transferred' always count in terms of 4k pages, even if
> 2 M & 1 GB pages are in use ?
Right now, IIRC, migration code scan pages in multiples of TARGET_PAGE_SIZE.
we don't have any code path to deal with pages larger than that.

However, I believe it makes sense to be specific that we're talking about
TARGET_PAGE_SIZE pages. In the future, we may then have separate lines
for each kind of page being transferred.

In a nutshell, we can have something in the lines of:
pages total:
  X 4K pages
  Y 2M pages
pages remaining:
  X' 4k pages
  Y' 2M pages
pages transferred:
  X'' 4k pages
  Y'' 2M pages

Of course, 2M would only be shown in this example if we are really using any.

How do you feel about that?

  reply	other threads:[~2009-05-21 14:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 23:20 [Qemu-devel] [PATCH] augment info migrate with page status Glauber Costa
2009-05-21 10:22 ` Dor Laor
2009-05-21 13:14   ` Anthony Liguori
2009-05-21 13:52   ` Glauber Costa
2009-05-21 14:40     ` Avi Kivity
2009-05-21 14:05 ` Daniel P. Berrange
2009-05-21 14:20   ` Glauber Costa [this message]
2009-05-21 14:58   ` Avi Kivity
2009-05-21 15:04     ` Daniel P. Berrange
2009-05-21 16:07       ` Glauber Costa
2009-05-21 23:41 ` [Qemu-devel] QEMU Official OS Support PAge Natalia Portillo
  -- strict thread matches above, loose matches on Subject: below --
2009-05-21 18:26 [Qemu-devel] [PATCH] augment info migrate with page status Glauber Costa
2009-05-21 19:17 Glauber Costa

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=20090521142015.GB24584@poweredge.glommer \
    --to=glommer@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.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 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).