All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] set migration max downtime
Date: Sun, 24 May 2009 14:47:58 -0500	[thread overview]
Message-ID: <4A19A46E.1070308@us.ibm.com> (raw)
In-Reply-To: <4A192A67.8050801@redhat.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>> Glauber Costa wrote:
>>> provide a monitor command to allow one to set the maximum
>>> downtime he is willing to suffer during migration, in miliseconds.
>>>   
>>
>> I think microseconds makes more sense.
>
> I prefer seconds (and bytes).

As a floating point value?

I would think the typical down time would be in the ms-us range so we're 
talking 0.030 - 0.000030 if we express in seconds.

Regards,

Anthony Liguori

  reply	other threads:[~2009-05-24 19:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 22:49 [Qemu-devel] [PATCH 0/2] Transfer of funds Glauber Costa
2009-05-21 22:49 ` [Qemu-devel] [PATCH 1/2] add non-arbitrary migration stop condition Glauber Costa
2009-05-21 22:49   ` [Qemu-devel] [PATCH 2/2] set migration max downtime Glauber Costa
2009-05-22  2:09     ` Anthony Liguori
2009-05-24 11:07       ` Avi Kivity
2009-05-24 19:47         ` Anthony Liguori [this message]
2009-05-24 19:52           ` Avi Kivity
2009-05-24 22:40             ` M. Warner Losh
2009-05-22  2:08   ` [Qemu-devel] [PATCH 1/2] add non-arbitrary migration stop condition Anthony Liguori
2009-05-24  8:29     ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2009-05-28 19:22 [Qemu-devel] [PATCH 0/2] Add non-arbitrary treshold for migration Glauber Costa
2009-05-28 19:22 ` [Qemu-devel] [PATCH 1/2] add non-arbitrary migration stop condition Glauber Costa
2009-05-28 19:22   ` [Qemu-devel] [PATCH 2/2] set migration max downtime 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=4A19A46E.1070308@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=glommer@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 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.