Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756293Ab3IYXZS (ORCPT ); Wed, 25 Sep 2013 19:25:18 -0400 Received: from e28smtp07.in.ibm.com ([122.248.162.7]:34705 "EHLO e28smtp07.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756274Ab3IYXZN (ORCPT ); Wed, 25 Sep 2013 19:25:13 -0400 From: "Srivatsa S. Bhat" Subject: [RFC PATCH v4 32/40] mm: Set pageblock migratetype when allocating regions from region allocator To: akpm@linux-foundation.org, mgorman@suse.de, dave@sr71.net, hannes@cmpxchg.org, tony.luck@intel.com, matthew.garrett@nebula.com, riel@redhat.com, arjan@linux.intel.com, srinivas.pandruvada@linux.intel.com, willy@linux.intel.com, kamezawa.hiroyu@jp.fujitsu.com, lenb@kernel.org, rjw@sisk.pl Cc: gargankita@gmail.com, paulmck@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com, andi@firstfloor.org, isimatu.yasuaki@jp.fujitsu.com, santosh.shilimkar@ti.com, kosaki.motohiro@gmail.com, srivatsa.bhat@linux.vnet.ibm.com, linux-pm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Date: Thu, 26 Sep 2013 04:50:59 +0530 Message-ID: <20130925232057.26184.12331.stgit@srivatsabhat.in.ibm.com> In-Reply-To: <20130925231250.26184.31438.stgit@srivatsabhat.in.ibm.com> References: <20130925231250.26184.31438.stgit@srivatsabhat.in.ibm.com> User-Agent: StGIT/0.14.3 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13092523-8878-0000-0000-000008FD52A5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2261 Lines: 52 We would like to maintain memory regions such that all memory pertaining to given a memory region serves allocations of a single migratetype. IOW, we don't want to permanently mix allocations of different migratetypes within the same region. So, when allocating a region from the region allocator to the page allocator, set the pageblock migratetype of all that memory to the migratetype for which the page allocator requested memory. Note that this still allows temporary sharing of pages between different migratetypes; it just ensures that there is no *permanent* mixing of migratetypes within a given memory region. An important advantage to be noted here is that the region allocator doesn't have to manage memory in a granularity lesser than a memory region, in *any* situation. This is because the freepage migratetype and the fallback mechanism allows temporary sharing of free memory between different migratetypes when the system is short on memory, but eventually all the memory gets freed to the original migratetype (because we set the pageblock migratetype of all the freepages appropriately when allocating regions). This greatly simplifies the design of the region allocator, since it doesn't have to keep track of memory in smaller chunks than a memory region. Signed-off-by: Srivatsa S. Bhat --- mm/page_alloc.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c index fd32533..c4cbd80 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1017,8 +1017,10 @@ static void __del_from_region_allocator(struct zone *zone, unsigned int order, reg_area = ®_alloc->region[region_id].region_area[order]; ralloc_list = ®_area->list; - list_for_each_entry(page, ralloc_list, lru) + list_for_each_entry(page, ralloc_list, lru) { set_freepage_migratetype(page, migratetype); + set_pageblock_migratetype(page, migratetype); + } free_list = &zone->free_area[order].free_list[migratetype]; -- 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/