From: "Luck, Tony" <tony.luck@intel.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Andi Kleen <ak@suse.de>, Paul Mackerras <paulus@samba.org>,
Andrew Morton <akpm@osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
"Protasevich, Natalie" <Natalie.Protasevich@unisys.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig
Date: Wed, 9 Aug 2006 10:58:54 -0700 [thread overview]
Message-ID: <20060809175854.GA14382@intel.com> (raw)
In-Reply-To: <1155025073.26277.18.camel@localhost>
On Tue, Aug 08, 2006 at 10:17:53AM +0200, Martin Schwidefsky wrote:
> "vmalloc reserve first; allocate pages later" would be a really nice
> feature. We could use this on s390 to implement the virtual mem_map
> array spanning the whole 64 bit address range (with holes in it). To
> make it perfect a "deallocate pages; keep vmalloc reserve" should be
> added, then we could free parts of the mem_map array again on hot memory
> remove.
IA-64 already has some arch. specific code to allocate a sparse
virtual memory map ... having generic code to do so would be
nice, but I foresee some chicken&egg problems in getting enough
of the vmalloc/vmap framework up & running before mem_map[] has
been allocated.
That and the hotplug memory folks don't like the virtual mem_map
code and have spurned it in favour of SPARSE.
-Tony
next prev parent reply other threads:[~2006-08-09 17:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 15:26 [PATCH] x86_64: Make NR_IRQS configurable in Kconfig Eric W. Biederman
2006-08-07 15:33 ` Andi Kleen
2006-08-07 15:55 ` Eric W. Biederman
2006-08-07 15:59 ` Randy.Dunlap
2006-08-07 16:11 ` Protasevich, Natalie
2006-08-07 16:17 ` Andi Kleen
2006-08-07 16:23 ` Protasevich, Natalie
2006-08-07 16:58 ` Eric W. Biederman
2006-08-07 16:44 ` Eric W. Biederman
2006-08-07 17:00 ` H. Peter Anvin
2006-08-07 17:46 ` Eric W. Biederman
2006-08-07 17:52 ` H. Peter Anvin
2006-08-07 17:30 ` Eric W. Biederman
2006-08-07 17:55 ` Randy.Dunlap
2006-08-07 18:16 ` Eric W. Biederman
2006-08-07 18:53 ` Eric W. Biederman
2006-08-07 19:04 ` Randy.Dunlap
2006-08-07 22:10 ` Eric W. Biederman
2006-08-07 23:55 ` Andrew Morton
2006-08-08 2:17 ` Andi Kleen
2006-08-08 2:41 ` Andrew Morton
2006-08-08 2:47 ` Arjan van de Ven
2006-08-08 5:47 ` [PATCH] x86_64: Auto size the per cpu area Eric W. Biederman
2006-08-08 6:01 ` Andrew Morton
2006-08-08 6:31 ` Eric W. Biederman
2006-08-08 6:01 ` Andi Kleen
2006-08-08 6:46 ` Eric W. Biederman
2006-08-08 6:48 ` Andi Kleen
2006-08-08 7:29 ` Eric W. Biederman
2006-08-08 5:09 ` [PATCH] x86_64: Make NR_IRQS configurable in Kconfig Paul Mackerras
2006-08-08 5:14 ` Andi Kleen
2006-08-08 8:17 ` Martin Schwidefsky
2006-08-09 17:58 ` Luck, Tony [this message]
2006-08-09 18:25 ` Dave Hansen
2006-08-10 12:55 ` Martin Schwidefsky
2006-08-10 14:40 ` Andy Whitcroft
2006-08-10 14:53 ` Martin Schwidefsky
2006-08-07 19:40 ` Adrian Bunk
2006-08-07 22:26 ` Eric W. Biederman
2006-08-07 23:06 ` Adrian Bunk
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=20060809175854.GA14382@intel.com \
--to=tony.luck@intel.com \
--cc=Natalie.Protasevich@unisys.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rdunlap@xenotime.net \
--cc=schwidefsky@de.ibm.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.