From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54829)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <amit.shah@redhat.com>) id 1Wts2s-0007WU-DG
	for qemu-devel@nongnu.org; Mon, 09 Jun 2014 01:23:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <amit.shah@redhat.com>) id 1Wts2g-0007eV-Tk
	for qemu-devel@nongnu.org; Mon, 09 Jun 2014 01:22:58 -0400
Received: from mx1.redhat.com ([209.132.183.28]:59025)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <amit.shah@redhat.com>) id 1Wts2g-0007e4-LY
	for qemu-devel@nongnu.org; Mon, 09 Jun 2014 01:22:46 -0400
Date: Mon, 9 Jun 2014 10:52:28 +0530
From: Amit Shah <amit.shah@redhat.com>
Message-ID: <20140609052228.GA25383@grmbl.mre>
References: <1395892646-30283-1-git-send-email-aik@ozlabs.ru>
	<20140606125036.GB27148@grmbl.mre> <5391F0CE.5040304@ozlabs.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5391F0CE.5040304@ozlabs.ru>
Subject: Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime
 from 30ms to 300ms
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, Juan Quintela <quintela@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org, "Dr . David Alan Gilbert" <dgilbert@redhat.com>

On (Sat) 07 Jun 2014 [02:48:14], Alexey Kardashevskiy wrote:
> On 06/06/2014 10:50 PM, Amit Shah wrote:
> > On (Thu) 27 Mar 2014 [14:57:26], Alexey Kardashevskiy wrote:
> >> The existing timeout is 30ms which on 100MB/s (1Gbit) gives us
> >> 3MB/s rate maximum. If we put some load on the guest, it is easy to
> >> get page dirtying rate too big so live migration will never complete.
> >> In the case of libvirt that means that the guest will be stopped
> >> anyway after a timeout specified in the "virsh migrate" command and
> >> this normally generates even bigger delay.
> >>
> >> This changes max_downtime to 300ms which seems to be more
> >> reasonable value.
> >>
> >> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> > 
> > Reviewed-by: Amit Shah <amit.shah@redhat.com>
> 
> Cool, thanks!
> 
> But what is next? The patch is > 2 months old and it is simple and
> everything but it did not make it to any tree so far :)

I'll pester Juan to get it in :-)

		Amit