From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750715AbWG0LQs (ORCPT ); Thu, 27 Jul 2006 07:16:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751133AbWG0LQs (ORCPT ); Thu, 27 Jul 2006 07:16:48 -0400 Received: from ug-out-1314.google.com ([66.249.92.171]:43224 "EHLO ug-out-1314.google.com") by vger.kernel.org with ESMTP id S1750715AbWG0LQr (ORCPT ); Thu, 27 Jul 2006 07:16:47 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mEjD3pgFgVwtoHYwQZy518NH8M6Aj7kriUQlWlfNd1L19fae0qb15QQ+uUho9XDfN/P47XxVILoha1BterCdLrO9eTZzJxJrP1Mbc/wzy0x1+I0+Cd4aFXmqgZxXaVEgAm/rwbZAIekaJZHNzyWtUVCgvV6OMCEmXe4w0s7g0hU= Message-ID: <6e0cfd1d0607270416g1248e93fi123b6ada852ff242@mail.gmail.com> Date: Thu, 27 Jul 2006 13:16:45 +0200 From: "Martin Schwidefsky" To: "Peter Zijlstra" Subject: Re: [PATCH] mm: inactive-clean list Cc: "Rik van Riel" , linux-mm , "Linus Torvalds" , "Andrew Morton" , linux-kernel In-Reply-To: <1153925104.2762.11.camel@taijtu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1153167857.31891.78.camel@lappy> <44C30E33.2090402@redhat.com> <6e0cfd1d0607260400r731489a1tfd9e6c5a197fb0bd@mail.gmail.com> <1153912268.2732.30.camel@taijtu> <6e0cfd1d0607260604w3e8636e4taaea4bc918397b34@mail.gmail.com> <1153925104.2762.11.camel@taijtu> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 7/26/06, Peter Zijlstra wrote: > Wouldn't we typically have all free pages > min_free in state U? > Also wouldn't all R/O mapped pages not also be V, all R/W mapped pages > and unmapped page-cache pages P like you state in your paper. Ahh, ok, I misunderstood. You want to keep the state changes for clean page cache pages, I assumed that you only want to make pages volatile if the get on the inactive_clean list and leave them stable if they are on one of the other two lists. > This patch would just increase the number of V pages with the tail end > of the guest LRU, which are typically the pages you would want to evict > (perhaps even add 5th guest state to indicate that these V pages are > preferable over the others?) Yes, that would help for architectures that cannot implement the potential-volatile state. > But isn't it so that for the gross over-commit scenario you outline the > host OS will have to swap out S pages eventually? My point was that you really have to distinguish between host memory pressure and guest memory pressure. -- blue skies, Martin