From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N6JD6-0006Pi-Om for qemu-devel@nongnu.org; Fri, 06 Nov 2009 02:26:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N6JD2-0006P1-18 for qemu-devel@nongnu.org; Fri, 06 Nov 2009 02:26:16 -0500 Received: from [199.232.76.173] (port=50260 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6JD1-0006Oy-Tr for qemu-devel@nongnu.org; Fri, 06 Nov 2009 02:26:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:11835) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N6JD1-0000dE-Ge for qemu-devel@nongnu.org; Fri, 06 Nov 2009 02:26:11 -0500 Message-ID: <4AF3CF8C.1030408@redhat.com> Date: Fri, 06 Nov 2009 09:26:04 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu References: <1257294485-27015-1-git-send-email-aliguori@us.ibm.com> <20091105163702.GC21630@shareable.org> <4AF30129.7080203@us.ibm.com> <200911051820.48878.arnd@arndb.de> <4AF3154F.8090901@redhat.com> <4AF36DE9.3040803@us.ibm.com> In-Reply-To: <4AF36DE9.3040803@us.ibm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Mark McLoughlin , Arnd Bergmann , Arnd Bergmann , Juan Quintela , Dustin Kirkland , qemu-devel@nongnu.org, Michael Tsirkin , Adam Litke On 11/06/2009 02:29 AM, Anthony Liguori wrote: >> Helpers are really bad. On launch, I find the fragile and hard to do >> proper error handling with (but that's probably just me). But the >> real problem is at runtime, if you have a 16GB guest then you have to >> write-protect 4M ptes and then kvm has to tear down or write protect >> (not sure which mmu notifier is called) 4M shadow ptes. Once that's >> done, the guest will have to fault its way back; that's at least 4M >> exits, around 10 seconds worth of cpu time to execute a couple of >> syscalls. > > > FWIW, with large pages, it's only 8k exits which comes out to about > 16ms. If nothing else, it's an argument for the important of > transparent large pages. > No, it's an argument against fork() of large programs. Transparent large pages are very important for performance, but speeding up fork() of large programs is not one of their reasons for existence. In any case we don't have them yet. Will you recommend people avoid hotplug until we have transparent large pages? And check that the qemu is actually using them (they'll be best effort, not a guarantee) before hotplug? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.