From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755880AbZHFNov (ORCPT ); Thu, 6 Aug 2009 09:44:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755210AbZHFNou (ORCPT ); Thu, 6 Aug 2009 09:44:50 -0400 Received: from mx2.redhat.com ([66.187.237.31]:60603 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754489AbZHFNou (ORCPT ); Thu, 6 Aug 2009 09:44:50 -0400 Message-ID: <4A7ADF78.20105@redhat.com> Date: Thu, 06 Aug 2009 16:49:44 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2 MIME-Version: 1.0 To: Rik van Riel CC: Wu Fengguang , Andrea Arcangeli , "Dike, Jeffrey G" , "Yu, Wilfred" , "Kleen, Andi" , Hugh Dickins , Andrew Morton , Christoph Lameter , KOSAKI Motohiro , Mel Gorman , LKML , linux-mm Subject: Re: [RFC] respect the referenced bit of KVM guest pages? References: <20090805024058.GA8886@localhost> <20090805155805.GC23385@random.random> <20090806100824.GO23385@random.random> <4A7AAE07.1010202@redhat.com> <20090806102057.GQ23385@random.random> <20090806105932.GA1569@localhost> <4A7AC201.4010202@redhat.com> <4A7AD6EB.9090208@redhat.com> In-Reply-To: <4A7AD6EB.9090208@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/06/2009 04:13 PM, Rik van Riel wrote: > Avi Kivity wrote: >> On 08/06/2009 01:59 PM, Wu Fengguang wrote: > >>> As a refinement, the static variable 'recent_all_referenced' could be >>> moved to struct zone or made a per-cpu variable. >> >> Definitely this should be made part of the zone structure, consider >> the original report where the problem occurs in a 128MB zone (where >> we can expect many pages to have their referenced bit set). > > The problem did not occur in a 128MB zone, but in a 128MB cgroup. > > Putting it in the zone means that the cgroup, which may have > different behaviour from the rest of the zone, due to excessive > memory pressure inside the cgroup, does not get the right > statistics. > Well, it should be per inactive list, whether it's a zone or a cgroup. What's the name of this thing? ("inactive list"?) error compiling committee.c: too many arguments to function