From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M8Jk4-0002xe-Rg
	for qemu-devel@nongnu.org; Sun, 24 May 2009 15:52:20 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M8Jjx-0002we-S1
	for qemu-devel@nongnu.org; Sun, 24 May 2009 15:52:18 -0400
Received: from [199.232.76.173] (port=35012 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M8Jjx-0002wb-J0
	for qemu-devel@nongnu.org; Sun, 24 May 2009 15:52:13 -0400
Received: from mx2.redhat.com ([66.187.237.31]:57498)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1M8Jjx-0003Tb-2h
	for qemu-devel@nongnu.org; Sun, 24 May 2009 15:52:13 -0400
Message-ID: <4A19A56D.2020303@redhat.com>
Date: Sun, 24 May 2009 22:52:13 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 2/2] set migration max downtime
References: <1242946174-30451-1-git-send-email-glommer@redhat.com>
	<1242946174-30451-2-git-send-email-glommer@redhat.com>
	<1242946174-30451-3-git-send-email-glommer@redhat.com>
	<4A160950.8020906@codemonkey.ws> <4A192A67.8050801@redhat.com>
	<4A19A46E.1070308@us.ibm.com>
In-Reply-To: <4A19A46E.1070308@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel@nongnu.org

Anthony Liguori wrote:
>> I prefer seconds (and bytes).
>
> As a floating point value?

Yes.  More than enough spacecraft have been lost due to errors in unit=20
conversion.

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

Just like we support suffixes for memory, we could support them for=20
time.  So your range would be 30ms - 30us (committing another crime=20
writing =B5s as us).

--=20
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.