From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 0/4] ia64 SPARSEMEM
Date: Thu, 26 May 2005 22:04:54 +0000 [thread overview]
Message-ID: <20050526220454.GL23448@localhost.localdomain> (raw)
In-Reply-To: <20050523175031.GC2783@localhost.localdomain>
David Mosberger wrote: [Thu May 26 2005, 04:09:06PM EDT]
> >>>>> On Tue, 24 May 2005 12:27:39 -0400, Bob Picco <bob.picco@hp.com> said:
>
> >> + * SECTION_SIZE_BITS 2^N: how big each section will be
>
> Bob> I don't perceive VIRTUAL_MEM_MAP as a nicer solution. Actually
> Bob> SPARSEMEM is a very elegant solution for memory holes and
> Bob> hotplug memory.
>
> Except that it requires configuration? What happens if
> SECTION_SIZE_BITS is chosen wrong or poorly for a given (perhaps new)
> platform?
>
> --david
> -
Yes I suppose this is a valid point. Choosing a bad value for a very
sparse address address space or machine with small quantity of memory could
consume lots of useless memory for section_map and/or reserved page
structures.
I'd prefer not to have a platform specific solution. This needs to be given
some more thought.
bob
next prev parent reply other threads:[~2005-05-26 22:04 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 [this message]
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
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=20050526220454.GL23448@localhost.localdomain \
--to=bob.picco@hp.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.