[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOJsxLE_iby+-EGzqXDc9D=Db7mm1NDDqdHqN_a+mZAQfLBrFA@mail.gmail.com>
Date: Tue, 31 Jan 2012 14:46:46 +0200
From: Pekka Enberg <penberg@...nel.org>
To: Maxime Coquelin <maxime.coquelin@...ricsson.com>
Cc: Mel Gorman <mel@....ul.ie>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linaro-mm-sig@...ts.linaro.org" <linaro-mm-sig@...ts.linaro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus WALLEIJ <linus.walleij@...ricsson.com>,
Andrea GALLO <andrea.gallo@...ricsson.com>,
Vincent GUITTOT <vincent.guittot@...ricsson.com>,
Philippe LANGLAIS <philippe.langlais@...ricsson.com>,
Loic PALLARDY <loic.pallardy@...ricsson.com>
Subject: Re: [RFCv1 3/6] PASR: mm: Integrate PASR in Buddy allocator
On Mon, Jan 30, 2012 at 6:52 PM, Maxime Coquelin
<maxime.coquelin@...ricsson.com> wrote:
>> What is more likely is that you will get pushed to doing something like
>> periodically scanning memory as part of a separate power management
>> module and calling into PASR if regions of memory that are found that
>> can be powered down in some ways.
>
> With this solution, we need in any case to add some hooks in the allocator
> to ensure the pages being allocated are refreshed.
Why do you insist on making this happen at page level when you're only
able to power off *much* larger chunks?
--
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