Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753603Ab0ASN0q (ORCPT ); Tue, 19 Jan 2010 08:26:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752596Ab0ASN0p (ORCPT ); Tue, 19 Jan 2010 08:26:45 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52057 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751337Ab0ASN0o (ORCPT ); Tue, 19 Jan 2010 08:26:44 -0500 Date: Tue, 19 Jan 2010 15:26:08 +0200 From: Gleb Natapov To: Pekka Enberg Cc: Minchan Kim , Alan Cox , linux-mm@kvack.org, kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, akpm@linux-foundation.org, andrew.c.morrow@gmail.com, "Paul E. McKenney" , Rik van Riel , Johannes Weiner Subject: Re: [PATCH v6] add MAP_UNLOCKED mmap flag Message-ID: <20100119132608.GQ14345@redhat.com> References: <20100118181942.GD22111@redhat.com> <20100118191031.0088f49a@lxorguk.ukuu.org.uk> <20100119071734.GG14345@redhat.com> <84144f021001182337o274c8ed3q8ce60581094bc2b9@mail.gmail.com> <20100119075205.GI14345@redhat.com> <84144f021001190007q54a334dfwed64189e6cf0b7c4@mail.gmail.com> <20100119082638.GK14345@redhat.com> <84144f021001190044s397c6665qb00af48235d2d818@mail.gmail.com> <1263905332.2163.11.camel@barrios-desktop> <84144f021001190518x450868eax2edfa5e16ff6e4b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84144f021001190518x450868eax2edfa5e16ff6e4b@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1306 Lines: 31 On Tue, Jan 19, 2010 at 03:18:11PM +0200, Pekka Enberg wrote: > On Tue, Jan 19, 2010 at 2:48 PM, Minchan Kim wrote: > > Gleb. How about using MADV_SEQUENTIAL on guest memory? > > It makes that pages of guest are moved into inactive reclaim list more > > fast. It means it is likely to swap out faster than other pages if it > > isn't hit during inactive list. > > Yeah, something like that but we don't want the readahead. OTOH, it's > not clear what Gleb's real problem is. Are the guest address spaces > anonymous or file backed? Anonymous. > Which parts of the emulator are swapped out > that are causing the problem? I don't want anything that can be used during guest runtime to be swapped out. And I run 2G guest in 512M container, so eventually everything is swapped out :) > Maybe it's a VM balancing issue that > mlock papers over? > There is no problem. I do measurements on how host swapping affects guest and I don't want qemu code to be swapped out. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/