From: Ingo Molnar <mingo@elte.hu>
To: kamezawa.hiroyu@jp.fujitsu.com
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>,
Andi Kleen <andi@firstfloor.org>, Gary Hade <garyhade@us.ibm.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Badari Pulavarty <pbadari@us.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
Chris McDermott <lcm@us.ibm.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option
Date: Sat, 6 Sep 2008 18:17:40 +0200 [thread overview]
Message-ID: <20080906161740.GB10238@elte.hu> (raw)
In-Reply-To: <9031244.1220716855172.kamezawa.hiroyu@jp.fujitsu.com>
* kamezawa.hiroyu@jp.fujitsu.com <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > Removing those limitations of kernel-space allocations should indeed
> > be done in baby steps - and whether it's worth turning such memory
> > into completely generic kernel memory is an open question.
>
> I think generic kernel space memory hotplug will never be available.
yeah, most likely. (It's possible technically even on a native kernel -
just very expensive to various aspects of the kernel.)
> > But the fact that a piece of memory is not fully generic is no
> > reason not to allow users to create special, capability-limited RAM
> > resources like they can already do via hugetlbfs or ramfs, as long
> > as the the capability limitations are advertised clearly.
>
> Hmm, adding a feature like
> - offline some memory at boot.
> - online-memory-as-hugeltb mode
>
> is useful for generic pc users ?
yeah - it's actually the way how hugetlb should be done. Plus expand
gbpages to hugetlbfs and hotplug memory on Barcelona CPUs and you can do
user-space apps that can run for a long time without any TLB misses.
_That_ might make sense to explore in practice. (i'm not holding my
breath though, TLB misses are _fast_ on the best x86 CPUs.)
But we wont be able to make such experiments without having the
capability on x86. So i'd like to break the catch-22 by accepting all
this into arch/x86, it certainly is simple and makes some sense, it's
just that i'm not that convinced about it personally at the moment.
So feel free to turn it all into a killer feature (make hugetlb backed
memory transparent to user-space, etc. etc.) that high-performance
computing users strive for and all that will change. Please send the
reshaped patches so we can move past the 'what if' discussion phase ;-)
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-09-06 16:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 17:21 Gary Hade
2008-09-05 17:44 ` Ingo Molnar
2008-09-05 18:14 ` Badari Pulavarty
2008-09-05 18:17 ` Ingo Molnar
2008-09-08 21:52 ` [PATCH] Cleanup to make remove_memory() arch neutral Badari Pulavarty
2008-09-09 0:56 ` Andrew Morton
2008-09-09 1:14 ` Randy Dunlap
2008-09-09 1:21 ` Yasunori Goto
2008-09-09 15:12 ` Badari Pulavarty
2008-09-08 21:56 ` [PATCH] x86: add memory hotremove config option Badari Pulavarty
2008-09-05 18:04 ` [PATCH] [RESEND] x86_64: " Andi Kleen
2008-09-05 18:31 ` Badari Pulavarty
2008-09-05 18:54 ` Andi Kleen
2008-09-05 22:34 ` Badari Pulavarty
2008-09-05 19:53 ` Gary Hade
2008-09-05 20:04 ` Andi Kleen
2008-09-05 21:54 ` Gary Hade
2008-09-06 0:01 ` Andi Kleen
2008-09-06 7:06 ` Yasunori Goto
2008-09-06 8:53 ` Andi Kleen
2008-09-08 5:52 ` Nick Piggin
2008-09-08 9:36 ` Andi Kleen
2008-09-08 9:46 ` Nick Piggin
2008-09-08 10:30 ` Andi Kleen
2008-09-08 11:19 ` Nick Piggin
2008-09-08 11:30 ` Andi Kleen
2008-09-08 13:48 ` Nick Piggin
2008-09-06 14:33 ` Ingo Molnar
2008-09-06 16:00 ` kamezawa.hiroyu
2008-09-06 16:17 ` Ingo Molnar [this message]
2008-09-06 16:05 ` kamezawa.hiroyu
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=20080906161740.GB10238@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=garyhade@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=pbadari@us.ibm.com \
--cc=x86@kernel.org \
--cc=y-goto@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox