Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765203AbYCFLOf (ORCPT ); Thu, 6 Mar 2008 06:14:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761132AbYCFLOZ (ORCPT ); Thu, 6 Mar 2008 06:14:25 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:42559 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759050AbYCFLOY (ORCPT ); Thu, 6 Mar 2008 06:14:24 -0500 Date: Thu, 6 Mar 2008 12:14:08 +0100 From: Ingo Molnar To: Andi Kleen Cc: "Rafael J. Wysocki" , Pavel Machek , kernel list , Thomas Gleixner Subject: Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo? Message-ID: <20080306111408.GM13391@elte.hu> References: <20080305090610.GA30024@atrey.karlin.mff.cuni.cz> <20080305093923.GA2049@atrey.karlin.mff.cuni.cz> <200803052312.37996.rjw@sisk.pl> <200803052331.42193.ak@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803052331.42193.ak@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1020 Lines: 24 * Andi Kleen wrote: > Just commenting on the subject. The 34TB are not an over/underflow. > x86-64 simply has so much address space reserved for vmalloc. It > doesn't mean of course that that much could be actually allocated in > real memory. btw., the exact amount of available vmalloc space on 64-bit x86 is 32 TB (32768 GB), or 0x0000200000000000 hexa. (this is still only 0.0002% of the complete 64-bit address space [25% of the 128 TB 64-bit kernel address space] so we've got plenty of room) but the first fundamental limit we'll hit on 64-bit is the 32-bit offset limit of binaries - this affects kernel modules, the kernel image, etc. We wont hit that anytime soon, but we'll eventually hit it. (user-space will be the first i guess) Ingo -- 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/