All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 0/4] ia64 SPARSEMEM
Date: Tue, 31 May 2005 18:15:17 +0000	[thread overview]
Message-ID: <20050531181517.GA16283@sgi.com> (raw)
In-Reply-To: <20050523175031.GC2783@localhost.localdomain>

On Mon, May 30, 2005 at 09:18:22AM +0900, KAMEZAWA Hiroyuki wrote:
> Hi Bob,
> >Another point to consider...
> >
> >Both RH & SuSE release a single kernel binary image that is used on all
> >platforms. IA64 discovers the platform type (Dig, SGI, HP, ...) during
> >boot & sets up platform callouts to platform specific functions. We
> >will need to select values for both CONFIG_SECTION_BITS &
> >CONFIG_PHYSICAL_MEMORY_BITS that work on all IA64 platforms (or make these
> >values configurable at runtime)
> >
> After reading e-mails,
> 	physical address size -- 50bits
> 	section size	      -- 32bits

A significant number of SGI systems contain 2GB memory chunks (4x512MB
DIMMS configured as a 2GB memory bank). I think these system would prefer
a section size of 31bits. Right?

I'm concerned that there may not be value of "section size" & "physical address size"
that is optimal across all of the various IA64 platforms.

(Functionally, everything appears to work fine. I'm in the process of running a
few benchmarks on a 64p system. More later....).


> will be good as a default.
> This can work on any ia64 platforms && Full-sized Hugetlb can be used 
> without any tuning.
> 
> If people want to hot-remove smaller memory sections, he should adjust the 
> params.
> 
> -- Kame

-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.



  parent reply	other threads:[~2005-05-31 18:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 17:50 [patch 0/4] ia64 SPARSEMEM Bob Picco
2005-05-24  3:29 ` David Mosberger
2005-05-24 14:33 ` Bob Picco
2005-05-24 16:27 ` Bob Picco
2005-05-26  0:32 ` Luck, Tony
2005-05-26 20:09 ` David Mosberger
2005-05-26 20:54 ` Bob Picco
2005-05-26 21:02 ` Dave Hansen
2005-05-26 21:34 ` Luck, Tony
2005-05-26 21:44 ` Jack Steiner
2005-05-26 21:51 ` Bob Picco
2005-05-26 22:03 ` Luck, Tony
2005-05-26 22:04 ` Bob Picco
2005-05-27  5:14 ` Yasunori Goto
2005-05-27 10:35 ` Bob Picco
2005-05-27 16:23 ` David Mosberger
2005-05-27 22:04 ` Jack Steiner
2005-05-30  0:18 ` KAMEZAWA Hiroyuki
2005-05-31 17:55 ` Luck, Tony
2005-05-31 18:14 ` Dave Hansen
2005-05-31 18:15 ` Jack Steiner [this message]
2005-05-31 21:41 ` Luck, Tony
2005-05-31 21:58 ` Dave Hansen
2005-06-01  1:37 ` Bob Picco
2005-06-01  9:14 ` Andy Whitcroft
2005-06-01 22:48 ` David Mosberger

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=20050531181517.GA16283@sgi.com \
    --to=steiner@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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.