From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42153) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFQsN-0006ND-J6 for qemu-devel@nongnu.org; Tue, 12 Mar 2013 11:12:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UFQsI-0005Op-K2 for qemu-devel@nongnu.org; Tue, 12 Mar 2013 11:12:27 -0400 Received: from mail-we0-x22f.google.com ([2a00:1450:400c:c03::22f]:37607) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFQsI-0005Oe-De for qemu-devel@nongnu.org; Tue, 12 Mar 2013 11:12:22 -0400 Received: by mail-we0-f175.google.com with SMTP id x8so4894539wey.20 for ; Tue, 12 Mar 2013 08:12:21 -0700 (PDT) Date: Tue, 12 Mar 2013 16:12:18 +0100 From: Stefan Hajnoczi Message-ID: <20130312151218.GA21551@stefanha-thinkpad.redhat.com> References: <513DDFA3.1020308@dlhnet.de> <20130312083515.GA18302@stefanha-thinkpad.redhat.com> <001482DC-A501-482A-986D-30B04AC9D116@dlhnet.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001482DC-A501-482A-986D-30B04AC9D116@dlhnet.de> Subject: Re: [Qemu-devel] [RFC] find_next_bit optimizations List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: Orit Wasserman , "qemu-devel@nongnu.org" , Corentin Chary , Paolo Bonzini On Tue, Mar 12, 2013 at 09:41:04AM +0100, Peter Lieven wrote: > > Am 12.03.2013 um 09:35 schrieb Stefan Hajnoczi : > > > On Mon, Mar 11, 2013 at 02:44:03PM +0100, Peter Lieven wrote: > >> I ever since had a few VMs which are very hard to migrate because of a lot of memory I/O. I found that finding the next dirty bit > >> seemed to be one of the culprits (apart from removing locking which Paolo is working on). > >> > >> I have to following proposal which seems to help a lot in my case. Just wanted to have some feedback. > > > > Hi Peter, > > Do you have any performance numbers for this patch? I'm just curious > > how big the win is. > > Hi Stefan, > > please see my recent email to the list with the final patch. > The win is up to 100%. Worst case execution time (whole > array is zero) is halved on x86_64. Thanks! Stefan