LKML Archive on
help / color / mirror / Atom feed
From: Andi Kleen <>
To: Ingo Molnar <>
Cc: "Rafael J. Wysocki" <>, Pavel Machek <>,
	kernel list <>,
	Thomas Gleixner <>
Subject: Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo?
Date: Thu, 6 Mar 2008 12:30:38 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> but the first fundamental limit we'll hit on 64-bit is the 32-bit offset

31bit to be pedantic.

> limit of binaries - this affects kernel modules, the kernel image, etc. 

If that ever happens just -fPIC mode would need to be supported
and a proper PLT for the references between modules and kernel. It would complicate 
the module loader slightly, but not too much.

> We wont hit that anytime soon, but we'll eventually hit it. (user-space 
> will be the first i guess)

I recently submitted a patch to fix the 2GB limit for user space
binaries (missing O_LARGEFILE). I think it made it into .25.

Newer gcc/binutils support the large code model so you could actually
try to generate binaries that big :-) e.g. some of the rtl-to-C compilers
seem to generate huge code so it might be actually useful.

Also of course you can always split the executable into ~2GB shared libraries.


  reply	other threads:[~2008-03-06 11:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  9:06 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
2008-03-06 11:30           ` Andi Kleen [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).