[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A7AA999.8050309@redhat.com>
Date: Thu, 06 Aug 2009 12:59:53 +0300
From: Avi Kivity <avi@...hat.com>
To: Wu Fengguang <fengguang.wu@...el.com>
CC: "Dike, Jeffrey G" <jeffrey.g.dike@...el.com>,
Rik van Riel <riel@...hat.com>,
"Yu, Wilfred" <wilfred.yu@...el.com>,
"Kleen, Andi" <andi.kleen@...el.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Mel Gorman <mel@....ul.ie>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>
Subject: Re: [RFC] respect the referenced bit of KVM guest pages?
On 08/06/2009 12:35 PM, Wu Fengguang wrote:
> On Thu, Aug 06, 2009 at 05:35:59PM +0800, Avi Kivity wrote:
>
>> On 08/06/2009 12:25 PM, Wu Fengguang wrote:
>>
>>>> So you're effectively running a 256M guest on a 128M host?
>>>>
>>>> Do cgroups have private active/inactive lists?
>>>>
>>>>
>>> Yes, and they reuse the same page reclaim routines with the global
>>> LRU lists.
>>>
>>>
>> Then this looks like a bug in the shadow accessed bit handling.
>>
>
> Yes. One question is: why only stack pages hurts if it is a
> general page reclaim problem?
>
Do we know for a fact that only stack pages suffer, or is it what has
been noticed?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists