All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <cl@linux.com>
Cc: Jack Steiner <steiner@sgi.com>,
	linux-mm@kvack.org, linux-ia64@vger.kernel.org
Subject: Re: Very large memory configurations:   > 16 TB
Date: Fri, 07 Jan 2011 16:56:32 +0000	[thread overview]
Message-ID: <20110107165632.GA7088@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.1101071027040.3014@router.home>


* Christoph Lameter <cl@linux.com> wrote:

> Andi put a description of the memory layout in
> Documentation/x86/x86_64/mm.txt. Seems to indicate that 64 TB was
> considered as a maximum when the memory layout for x86_64 was set up:

Yes, that document was rather incomplete and does not really answer Jack's 
questions, that's why i sent this more complete description originally:

  http://lkml.indiana.edu/hypermail/linux/kernel/0812.2/00292.html

a few years ago, answering a similar question.

Thanks,

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <cl@linux.com>
Cc: Jack Steiner <steiner@sgi.com>,
	linux-mm@kvack.org, linux-ia64@vger.kernel.org
Subject: Re: Very large memory configurations:   > 16 TB
Date: Fri, 7 Jan 2011 17:56:32 +0100	[thread overview]
Message-ID: <20110107165632.GA7088@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.1101071027040.3014@router.home>


* Christoph Lameter <cl@linux.com> wrote:

> Andi put a description of the memory layout in
> Documentation/x86/x86_64/mm.txt. Seems to indicate that 64 TB was
> considered as a maximum when the memory layout for x86_64 was set up:

Yes, that document was rather incomplete and does not really answer Jack's 
questions, that's why i sent this more complete description originally:

  http://lkml.indiana.edu/hypermail/linux/kernel/0812.2/00292.html

a few years ago, answering a similar question.

Thanks,

	Ingo

--
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>

  reply	other threads:[~2011-01-07 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 17:09 Very large memory configurations: > 16 TB Jack Steiner
2011-01-06 17:09 ` 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 [this message]
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=20110107165632.GA7088@elte.hu \
    --to=mingo@elte.hu \
    --cc=cl@linux.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=steiner@sgi.com \
    /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.