Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755472Ab3DTPUP (ORCPT ); Sat, 20 Apr 2013 11:20:15 -0400 Received: from mail-da0-f48.google.com ([209.85.210.48]:46872 "EHLO mail-da0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755331Ab3DTPUH (ORCPT ); Sat, 20 Apr 2013 11:20:07 -0400 Message-ID: <5172B21E.9000805@gmail.com> Date: Sat, 20 Apr 2013 23:19:58 +0800 From: Jiang Liu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Russell King - ARM Linux CC: Andrew Morton , Jiang Liu , David Rientjes , Wen Congyang , Mel Gorman , Minchan Kim , KAMEZAWA Hiroyuki , Michal Hocko , James Bottomley , Sergei Shtylyov , David Howells , Mark Salter , Jianguo Wu , linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v4, part3 13/41] mm/ARM: prepare for removing num_physpages and simplify mem_init() References: <1365258760-30821-1-git-send-email-jiang.liu@huawei.com> <1365258760-30821-14-git-send-email-jiang.liu@huawei.com> <20130419165429.GA14496@n2100.arm.linux.org.uk> In-Reply-To: <20130419165429.GA14496@n2100.arm.linux.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3743 Lines: 105 On 04/20/2013 12:54 AM, Russell King - ARM Linux wrote: > On Sat, Apr 06, 2013 at 10:32:12PM +0800, Jiang Liu wrote: >> Prepare for removing num_physpages and simplify mem_init(). >> >> Signed-off-by: Jiang Liu >> Cc: Russell King >> Cc: Catalin Marinas >> Cc: Will Deacon >> Cc: linux-arm-kernel@lists.infradead.org >> Cc: linux-kernel@vger.kernel.org >> --- >> arch/arm/mm/init.c | 47 ++--------------------------------------------- >> 1 file changed, 2 insertions(+), 45 deletions(-) >> >> diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c >> index add4fcb..7a911d1 100644 >> --- a/arch/arm/mm/init.c >> +++ b/arch/arm/mm/init.c >> @@ -582,9 +582,6 @@ static void __init free_highpages(void) >> */ >> void __init mem_init(void) >> { >> - unsigned long reserved_pages, free_pages; >> - struct memblock_region *reg; >> - int i; >> #ifdef CONFIG_HAVE_TCM >> /* These pointers are filled in on TCM detection */ >> extern u32 dtcm_end; >> @@ -605,47 +602,7 @@ void __init mem_init(void) >> >> free_highpages(); >> >> - reserved_pages = free_pages = 0; >> - >> - for_each_bank(i, &meminfo) { >> - struct membank *bank = &meminfo.bank[i]; >> - unsigned int pfn1, pfn2; >> - struct page *page, *end; >> - >> - pfn1 = bank_pfn_start(bank); >> - pfn2 = bank_pfn_end(bank); >> - >> - page = pfn_to_page(pfn1); >> - end = pfn_to_page(pfn2 - 1) + 1; >> - >> - do { >> - if (PageReserved(page)) >> - reserved_pages++; >> - else if (!page_count(page)) >> - free_pages++; >> - page++; >> - } while (page < end); >> - } >> - >> - /* >> - * Since our memory may not be contiguous, calculate the >> - * real number of pages we have in this system >> - */ >> - printk(KERN_INFO "Memory:"); >> - num_physpages = 0; >> - for_each_memblock(memory, reg) { >> - unsigned long pages = memblock_region_memory_end_pfn(reg) - >> - memblock_region_memory_base_pfn(reg); >> - num_physpages += pages; >> - printk(" %ldMB", pages >> (20 - PAGE_SHIFT)); >> - } >> - printk(" = %luMB total\n", num_physpages >> (20 - PAGE_SHIFT)); >> - >> - printk(KERN_NOTICE "Memory: %luk/%luk available, %luk reserved, %luK highmem\n", >> - nr_free_pages() << (PAGE_SHIFT-10), >> - free_pages << (PAGE_SHIFT-10), >> - reserved_pages << (PAGE_SHIFT-10), >> - totalhigh_pages << (PAGE_SHIFT-10)); >> + mem_init_print_info(NULL); > > I'm concerned about this. We explicitly do not use the memblock information > when walking the memory above for the reserved/free pages because memblock > merges the various banks of memory together - and those may cross sparsemem > boundaries. Any crossing of the sparsemem boundaries needs the struct page > pointer to be re-evaluated because it can be part of a different array of > such things. > > Where's the rest of the patches? > Hi Russel, Thanks for review the patch. You may find the patch introducing mem_init_print_info() at: http://marc.info/?l=linux-mm&m=136525938817934&w=2 Basically it prints standard memory statistics info as below for all architectures without walking the page structure array. Memory: 7744624K/8074824K available (6969K kernel code, 1011K data, 2828K rodata, 1016K init, 9640K bss, 330200K reserved) On the other hand, the patch does change information printed on boot, especially it doesn't print size of each memory block. If needed, I can revert the code to print size of each memory block. Regards! Gerry -- 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/