Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751467Ab1FPEU6 (ORCPT ); Thu, 16 Jun 2011 00:20:58 -0400 Received: from e23smtp02.au.ibm.com ([202.81.31.144]:37063 "EHLO e23smtp02.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750731Ab1FPEU5 (ORCPT ); Thu, 16 Jun 2011 00:20:57 -0400 Date: Thu, 16 Jun 2011 09:50:44 +0530 From: Ankita Garg To: KAMEZAWA Hiroyuki Cc: linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-pm@lists.linux-foundation.org, svaidy@linux.vnet.ibm.com, thomas.abraham@linaro.org Subject: Re: [PATCH 00/10] mm: Linux VM Infrastructure to support Memory Power Management Message-ID: <20110616042044.GA28563@in.ibm.com> Reply-To: Ankita Garg References: <1306499498-14263-1-git-send-email-ankita@in.ibm.com> <20110613134701.2b23b8d8.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110613134701.2b23b8d8.kamezawa.hiroyu@jp.fujitsu.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1927 Lines: 53 Hi, On Mon, Jun 13, 2011 at 01:47:01PM +0900, KAMEZAWA Hiroyuki wrote: > On Fri, 27 May 2011 18:01:28 +0530 > Ankita Garg wrote: > > > Hi, > > > > I'm sorry if you've answered already. > > Is memory hotplug is too bad and cannot be enhanced for this purpose ? > > I wonder > - make section-size smaller (IIUC, IBM's system has 16MB section size) > > - add per section statistics > > - add a kind of balloon driver which does software memory offline > (which means making a contiguous chunk of free pages of section_size > by page migration) in background with regard to memory usage statistics. > If system says "need more memory!", balloon driver can online pages. > > can work for your purpose. It can allow you page isolatation and > controls in 16MB unit. If you need whole rework of memory hotplug, I think > it's better to rewrite memory hotplug, too. > Interesting idea, but a few issues - - Correctly predicting memory pressure is difficult and thereby being able to online the required pages at the right time could be a challenge - Memory hotplug is a heavy operation, so the overhead involved may be high - Powering off memory is just one of the ways in which memory power could be saved. The platform can also dynamically transition areas of memory into a content-preserving lower power state if it is not referenced for a pre-defined threshold of time. In such a case, we would need a mechanism to soft offline the pages - i.e, no new allocations to be directed to that memory -- Regards, Ankita Garg (ankita@in.ibm.com) Linux Technology Center IBM India Systems & Technology Labs, Bangalore, India -- 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/