Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756501Ab3E2FkM (ORCPT ); Wed, 29 May 2013 01:40:12 -0400 Received: from e23smtp03.au.ibm.com ([202.81.31.145]:53302 "EHLO e23smtp03.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752417Ab3E2FkG (ORCPT ); Wed, 29 May 2013 01:40:06 -0400 Message-ID: <51A593F1.5090200@linux.vnet.ibm.com> Date: Wed, 29 May 2013 11:06:49 +0530 From: "Srivatsa S. Bhat" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0 MIME-Version: 1.0 To: Phillip Susi CC: Simon Jeons , akpm@linux-foundation.org, mgorman@suse.de, matthew.garrett@nebula.com, dave@sr71.net, rientjes@google.com, riel@redhat.com, arjan@linux.intel.com, srinivas.pandruvada@linux.intel.com, maxime.coquelin@stericsson.com, loic.pallardy@stericsson.com, kamezawa.hiroyu@jp.fujitsu.com, lenb@kernel.org, rjw@sisk.pl, gargankita@gmail.com, paulmck@linux.vnet.ibm.com, amit.kachhap@linaro.org, svaidy@linux.vnet.ibm.com, andi@firstfloor.org, wujianguo@huawei.com, kmpark@infradead.org, thomas.abraham@linaro.org, santosh.shilimkar@ti.com, linux-pm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v2 00/15][Sorted-buddy] mm: Memory Power Management References: <20130409214443.4500.44168.stgit@srivatsabhat.in.ibm.com> <5170D781.3000102@gmail.com> <5170EE4F.9030908@linux.vnet.ibm.com> <51A50EC4.4090108@ubuntu.com> In-Reply-To: <51A50EC4.4090108@ubuntu.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13052905-6102-0000-0000-0000039A04A8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1634 Lines: 36 On 05/29/2013 01:38 AM, Phillip Susi wrote: > > On 4/19/2013 3:12 AM, Srivatsa S. Bhat wrote: >> But going further, as I had mentioned in my TODO list, we can be >> smarter than this while doing compaction to evacuate memory regions >> - we can choose to migrate only the active pages, and leave the >> inactive pages alone. Because, the goal is to actually consolidate >> the *references* and not necessarily the *allocations* themselves. > > That would help with keeping references compact to allow use of the > low power states, but it would also be nice to keep allocations > compact, and completely power off a bank of ram with no allocations. > That is a very good point, thanks! But one of the differences we have to keep in mind is that powering off a bank requires intervention from the OS (ie., OS should initiate the power-off, because we lose the contents on power-off) whereas going to lower power states can be mostly done automatically by the hardware (because it is content-preserving). But powering-off unused banks of RAM (using techniques such as PASR - Partial Array Self Refresh) can give us more power-savings than just entering lower power states. So yes, keeping allocations consolidated has that additional advantage. And the sorted-buddy design of the page allocator helps us achieve that. Thanks a lot for your inputs, Phillip! Regards, Srivatsa S. Bhat -- 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/