From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M8Jfz-000297-Oj for qemu-devel@nongnu.org; Sun, 24 May 2009 15:48:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M8Jfu-00026Z-3u for qemu-devel@nongnu.org; Sun, 24 May 2009 15:48:06 -0400 Received: from [199.232.76.173] (port=52657 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8Jfu-00026N-0X for qemu-devel@nongnu.org; Sun, 24 May 2009 15:48:02 -0400 Received: from e8.ny.us.ibm.com ([32.97.182.138]:51885) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M8Jft-0002zz-LF for qemu-devel@nongnu.org; Sun, 24 May 2009 15:48:01 -0400 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e8.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n4OJbk29029124 for ; Sun, 24 May 2009 15:37:46 -0400 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n4OJm0OU234002 for ; Sun, 24 May 2009 15:48:00 -0400 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n4OJjuI0004007 for ; Sun, 24 May 2009 15:45:56 -0400 Message-ID: <4A19A46E.1070308@us.ibm.com> Date: Sun, 24 May 2009 14:47:58 -0500 From: Anthony Liguori 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> In-Reply-To: <4A192A67.8050801@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Glauber Costa , qemu-devel@nongnu.org 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