From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59029) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UU97C-0001hY-Fc for qemu-devel@nongnu.org; Mon, 22 Apr 2013 01:16:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UU97B-0004NT-FS for qemu-devel@nongnu.org; Mon, 22 Apr 2013 01:16:34 -0400 Received: from g4t0014.houston.hp.com ([15.201.24.17]:5492) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UU97B-0004Mm-B6 for qemu-devel@nongnu.org; Mon, 22 Apr 2013 01:16:33 -0400 Message-ID: <5174C7AA.5040701@hp.com> Date: Sun, 21 Apr 2013 22:16:26 -0700 From: Chegu Vinod MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4] Add option to mlock qemu and guest memory List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Satoru Moriya , qemu-devel qemu-devel Hi Satoru, FYI... I had tried to use this change earlier and it did show some improvements in perf. (due to reduced exits). But as expected mlockall () on large sized guests adds a considerable delay in boot time. For e.g. on an 8 socket Westmere box => a 256G guest : took an additional ~2+ mins to boot and a 512G guest took an additional ~5+ mins to boot. This is mainly due to long time spent in trying to clear all the pages. 77.96% 35728 qemu-system-x86 [kernel.kallsyms] [k] clear_page_c | --- clear_page_c hugetlb_no_page hugetlb_fault follow_hugetlb_page __get_user_pages __mlock_vma_pages_range __mm_populate vm_mmap_pgoff sys_mmap_pgoff sys_mmap system_call __GI___mmap64 qemu_ram_alloc_from_ptr qemu_ram_alloc memory_region_init_ram pc_memory_init pc_init1 pc_init_pci main __libc_start_main Need to have a faster way to clear pages. Vinod