From patchwork Fri Aug 30 13:24:40 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Srivatsa S. Bhat" X-Patchwork-Id: 2852063 Return-Path: X-Original-To: patchwork-linux-pm@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork1.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork1.web.kernel.org (Postfix) with ESMTP id 830929F313 for ; Fri, 30 Aug 2013 13:29:05 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 631B2205F1 for ; Fri, 30 Aug 2013 13:29:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A1503205ED for ; Fri, 30 Aug 2013 13:28:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756524Ab3H3N2q (ORCPT ); Fri, 30 Aug 2013 09:28:46 -0400 Received: from e39.co.us.ibm.com ([32.97.110.160]:43910 "EHLO e39.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756635Ab3H3N2p (ORCPT ); Fri, 30 Aug 2013 09:28:45 -0400 Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 30 Aug 2013 07:28:44 -0600 Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 30 Aug 2013 07:28:43 -0600 Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id F04B23E4003E; Fri, 30 Aug 2013 07:28:42 -0600 (MDT) Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7UDSgTX206900; Fri, 30 Aug 2013 07:28:42 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r7UDSaZN014485; Fri, 30 Aug 2013 07:28:42 -0600 Received: from srivatsabhat.in.ibm.com ([9.79.248.196]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7UDSQPb013868; Fri, 30 Aug 2013 07:28:28 -0600 From: "Srivatsa S. Bhat" Subject: [RFC PATCH v3 34/35] mm: Set pageblock migratetype when allocating regions from region allocator To: akpm@linux-foundation.org, mgorman@suse.de, hannes@cmpxchg.org, tony.luck@intel.com, matthew.garrett@nebula.com, dave@sr71.net, 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: Fri, 30 Aug 2013 18:54:40 +0530 Message-ID: <20130830132437.4947.12826.stgit@srivatsabhat.in.ibm.com> In-Reply-To: <20130830131221.4947.99764.stgit@srivatsabhat.in.ibm.com> References: <20130830131221.4947.99764.stgit@srivatsabhat.in.ibm.com> User-Agent: StGIT/0.14.3 MIME-Version: 1.0 X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13083013-9332-0000-0000-00000141DA64 Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org X-Spam-Status: No, score=-9.0 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP 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(-) -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/mm/page_alloc.c b/mm/page_alloc.c index e303351..1312546 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1016,8 +1016,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];