From: Christoph Lameter <clameter@sgi.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux-mm@kvack.org, linux-ia64@vger.kernel.org,
linux-arch@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 0/8] Sparsemem Virtual Memmap V4
Date: Tue, 22 May 2007 17:42:27 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705221730420.19465@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <exportbomb.1179873917@pinky>
We will need this fix to sparsemem on IA64. I hope this will not cause
other issues in sparsemem?
IA64: Increase maximum physmem size to cover 8 petabyte
We currently can support these large configurations only with Discontigmem.
Increase sparsemems max physmem bits to also be able to handle 8 petabyte.
Discontigmem supports up to 16 petabyte but I will need to use bit 53 to
flag vmemmap addresses for the TLB handler. It seems that the currently
used bit 60 for the 16M configuration is not supported by a certain
virtualization technique.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
Index: linux-2.6.22-rc2/include/asm-ia64/sparsemem.h
===================================================================
--- linux-2.6.22-rc2.orig/include/asm-ia64/sparsemem.h 2007-05-22 17:28:04.000000000 -0700
+++ linux-2.6.22-rc2/include/asm-ia64/sparsemem.h 2007-05-22 17:28:37.000000000 -0700
@@ -8,7 +8,7 @@
*/
#define SECTION_SIZE_BITS (30)
-#define MAX_PHYSMEM_BITS (50)
+#define MAX_PHYSMEM_BITS (53)
#ifdef CONFIG_FORCE_MAX_ZONEORDER
#if ((CONFIG_FORCE_MAX_ZONEORDER - 1 + PAGE_SHIFT) > SECTION_SIZE_BITS)
#undef SECTION_SIZE_BITS
--
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-05-23 0:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 22:57 Andy Whitcroft
2007-05-22 22:58 ` [PATCH 1/8] sparsemem: clean up spelling error in comments Andy Whitcroft
2007-05-22 22:58 ` [PATCH 2/8] sparsemem: record when a section has a valid mem_map Andy Whitcroft
2007-05-22 22:59 ` [PATCH 3/8] Generic Virtual Memmap support for SPARSEMEM V4 Andy Whitcroft
2007-05-23 5:15 ` Christoph Lameter
2007-05-23 7:07 ` Stephen Rothwell
2007-05-22 23:00 ` [PATCH 4/8] x86_64: SPARSEMEM_VMEMMAP 2M page size support Andy Whitcroft
2007-05-22 23:00 ` [PATCH 5/8] IA64: SPARSEMEM_VMEMMAP 16K " Andy Whitcroft
2007-05-23 5:12 ` Christoph Lameter
2007-05-22 23:01 ` [PATCH 6/8] IA64: SPARSEMEM_VMEMMAP 16M " Andy Whitcroft
2007-05-22 23:01 ` [PATCH 7/8] SPARC64: SPARSEMEM_VMEMMAP support Andy Whitcroft
2007-05-22 23:02 ` [PATCH 8/8] ppc64: " Andy Whitcroft
2007-05-22 23:52 ` [PATCH 0/8] Sparsemem Virtual Memmap V4 Christoph Lameter
2007-05-23 0:00 ` Christoph Lameter
2007-05-23 0:42 ` Christoph Lameter [this message]
2007-05-23 4:16 ` David Miller, Andy Whitcroft
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.0705221730420.19465@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=apw@shadowen.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.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