From: Jack Steiner <steiner@sgi.com>
To: linux-mm@kvack.org, mingo@elte.hu
Cc: linux-ia64@vger.kernel.org
Subject: Very large memory configurations: > 16 TB
Date: Thu, 06 Jan 2011 17:09:42 +0000 [thread overview]
Message-ID: <20110106170942.GA8253@sgi.com> (raw)
SGI is currently developing an x86_64 system with more than 16TB of memory per
SSI. As far as I can tell, this should be supported. The relevant definitions
such as MAX_PHYSMEM_BITS appear ok.
One area of concern is page counts. Exceeding 16TB will also exceed MAX_INT
page frames. The kernel (at least in all places I've found) keep pagecounts
in longs.
Have I missed anything? Should this > 16TB work? Are there any kernel problems or
problems with user tools that anyone knows of.
Any help or pointers to potential problem areas would be appreciated...
---
Jack Steiner (steiner@sgi.com)
SGI - Silicon Graphics, Inc.
WARNING: multiple messages have this Message-ID (diff)
From: Jack Steiner <steiner@sgi.com>
To: linux-mm@kvack.org, mingo@elte.hu
Cc: linux-ia64@vger.kernel.org
Subject: Very large memory configurations: > 16 TB
Date: Thu, 6 Jan 2011 11:09:42 -0600 [thread overview]
Message-ID: <20110106170942.GA8253@sgi.com> (raw)
SGI is currently developing an x86_64 system with more than 16TB of memory per
SSI. As far as I can tell, this should be supported. The relevant definitions
such as MAX_PHYSMEM_BITS appear ok.
One area of concern is page counts. Exceeding 16TB will also exceed MAX_INT
page frames. The kernel (at least in all places I've found) keep pagecounts
in longs.
Have I missed anything? Should this > 16TB work? Are there any kernel problems or
problems with user tools that anyone knows of.
Any help or pointers to potential problem areas would be appreciated...
---
Jack Steiner (steiner@sgi.com)
SGI - Silicon Graphics, Inc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2011-01-06 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 17:09 Jack Steiner [this message]
2011-01-06 17:09 ` Very large memory configurations: > 16 TB Jack Steiner
2011-01-07 12:16 ` Michel Lespinasse
2011-01-07 12:16 ` Michel Lespinasse
2011-01-07 12:51 ` Ingo Molnar
2011-01-07 12:51 ` Ingo Molnar
2011-01-07 16:31 ` Christoph Lameter
2011-01-07 16:31 ` Christoph Lameter
2011-01-07 16:56 ` Ingo Molnar
2011-01-07 16:56 ` Ingo Molnar
2011-01-07 17:14 ` Christoph Lameter
2011-01-07 17:14 ` Christoph Lameter
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=20110106170942.GA8253@sgi.com \
--to=steiner@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.