From: Christoph Lameter <clameter@sgi.com>
To: Martin Bligh <mbligh@google.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"nickpiggin@yahoo.com.au" <nickpiggin@yahoo.com.au>,
"Lee.Schermerhorn@hp.com" <Lee.Schermerhorn@hp.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] overwride page->mapping [0/3] intro
Date: Wed, 12 Sep 2007 12:17:41 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709121214240.1934@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <46E83A19.2090604@google.com>
On Wed, 12 Sep 2007, Martin Bligh wrote:
> Because nobody (sane) has 16TB of memory? ;-)
Both our IA64 and the upcoming x86_64 line have the capability to address
more than 16TB of memory.
include/asm-ia64/sparsemem.h has
#define MAX_PHYSMEM_BITS (50)
(which is too low. We may have 4 Petabytes configurations sson so we want
this to be 54 or so)
and we are working on increasing x86_64 ....
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-09-12 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 2:43 KAMEZAWA Hiroyuki
2007-09-12 2:45 ` [RFC][PATCH] overwride page->mapping [1/3] cleanup KAMEZAWA Hiroyuki
2007-09-12 2:47 ` [RFC][PATCH] overwride page->mapping [2/3] page_mapping_info KAMEZAWA Hiroyuki
2007-09-12 2:48 ` [RFC][PATCH] override page->mapping [3/3] mlock counter per page KAMEZAWA Hiroyuki
2007-09-12 8:42 ` [RFC][PATCH] overwride page->mapping [0/3] intro Balbir Singh
2007-09-12 13:28 ` KAMEZAWA Hiroyuki
2007-09-12 19:10 ` Christoph Lameter
2007-09-12 19:12 ` Martin Bligh
2007-09-12 19:17 ` Christoph Lameter [this message]
2007-09-13 0:32 ` KAMEZAWA Hiroyuki
2007-09-13 1:05 ` Christoph Lameter
2007-09-13 1:27 ` KAMEZAWA Hiroyuki
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=Pine.LNX.4.64.0709121214240.1934@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@google.com \
--cc=nickpiggin@yahoo.com.au \
/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