From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo?
Date: Thu, 6 Mar 2008 12:14:08 +0100 [thread overview]
Message-ID: <20080306111408.GM13391@elte.hu> (raw)
In-Reply-To: <200803052331.42193.ak@suse.de>
* Andi Kleen <ak@suse.de> 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
next prev parent reply other threads:[~2008-03-06 11:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 9:06 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo? Pavel Machek
2008-03-05 9:36 ` Pavel Machek
2008-03-05 9:39 ` Pavel Machek
2008-03-05 22:12 ` Rafael J. Wysocki
2008-03-05 22:31 ` Andi Kleen
2008-03-06 11:14 ` Ingo Molnar [this message]
2008-03-06 11:30 ` Andi Kleen
2008-03-06 21:06 ` Ingo Molnar
2008-03-06 10:43 ` Pavel Machek
2008-03-05 19:49 ` Christian Kujau
2008-03-05 21:11 ` Hugh Dickins
2008-03-05 21:21 ` Pavel Machek
2008-03-05 21:36 ` Hugh Dickins
2008-03-05 22:11 ` Christian Kujau
2008-03-05 23:21 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080306111408.GM13391@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox