Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753763Ab3FYTDp (ORCPT ); Tue, 25 Jun 2013 15:03:45 -0400 Received: from mail-ie0-f171.google.com ([209.85.223.171]:60681 "EHLO mail-ie0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752502Ab3FYTDm (ORCPT ); Tue, 25 Jun 2013 15:03:42 -0400 MIME-Version: 1.0 In-Reply-To: <51C9E83A.8070700@sgi.com> References: <1371831934-156971-1-git-send-email-nzimmer@sgi.com> <20130621165142.GA32125@kroah.com> <51C48745.9030304@zytor.com> <20130621185056.GA23473@kroah.com> <51C4C5F3.3050800@sgi.com> <51C9D4ED.5070805@sgi.com> <51C9DEC1.6030602@zytor.com> <51C9E523.7000803@zytor.com> <51C9E83A.8070700@sgi.com> Date: Tue, 25 Jun 2013 12:03:42 -0700 X-Google-Sender-Auth: XMTYiYVIED2QB1I2vWtILhlVOJo Message-ID: Subject: Re: [RFC 0/2] Delay initializing of large sections of memory From: Yinghai Lu To: Mike Travis , "H. Peter Anvin" , Ingo Molnar Cc: Greg KH , Nathan Zimmer , Robin Holt , Rob Landley , Thomas Gleixner , Andrew Morton , "the arch/x86 maintainers" , linux-doc@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 801 Lines: 18 > It is worth experimenting with but the big question would be, > if it still avoids the very expensive "memmap_init_zone" and > it's sub-functions using huge expanses of memory. I'll do some > experimenting as soon as I can. Our 32TB system is being > brought back to 16TB (we found a number of problems as we > get closer and closer to the 64TB limit), but that's still > a significant size. According to Intel SDM, CPU could support 52bits physical addressing. So how linux kernel will handle it? as we only have 48bits virtual addressing. Yinghai -- 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/