From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752098AbbFZLZn (ORCPT ); Fri, 26 Jun 2015 07:25:43 -0400 Received: from szxga03-in.huawei.com ([119.145.14.66]:24200 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751812AbbFZLZg (ORCPT ); Fri, 26 Jun 2015 07:25:36 -0400 Message-ID: <558D368F.8030900@huawei.com> Date: Fri, 26 Jun 2015 19:25:03 +0800 From: Xishi Qiu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Mel Gorman CC: Andrew Morton , Vlastimil Babka , Johannes Weiner , , David Rientjes , , Linux MM , LKML Subject: Re: [PATCH] mm: fix set pageblock migratetype when boot References: <558D24C1.5020901@huawei.com> <20150626110424.GI26927@suse.de> In-Reply-To: <20150626110424.GI26927@suse.de> Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.25.179] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.558D36A0.0198,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 4235cd5551406be064550da76d4a37de Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2015/6/26 19:04, Mel Gorman wrote: > On Fri, Jun 26, 2015 at 06:09:05PM +0800, Xishi Qiu wrote: >> memmap_init_zone() >> ... >> if ((z->zone_start_pfn <= pfn) >> && (pfn < zone_end_pfn(z)) >> && !(pfn & (pageblock_nr_pages - 1))) >> set_pageblock_migratetype(page, MIGRATE_MOVABLE); >> ... >> >> If the pfn does not align to pageblock, it will not init the migratetype. > > What important impact does that have? It should leave a partial pageblock > as MIGRATE_UNMOVABLE which is fine by me. > Hi Mel, The impact is less, it's OK to ignore it. Thanks, Xishi Qiu >> So call it for every page, it will takes more time, but it doesn't matter, >> this function will be called only in boot or hotadd memory. >> > > It's a lot of additional overhead to add to memory initialisation. It > would need to be for an excellent reason with no alternative solution. >