Re: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Saturday, September 6, 2008 - 9:17 am

* kamezawa.hiroyu@jp.fujitsu.com <kamezawa.hiroyu@jp.fujitsu.com> wrote:


yeah, most likely. (It's possible technically even on a native kernel - 
just very expensive to various aspects of the kernel.)


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
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Re: [PATCH] [RESEND] x86_64: add memory hotremove conf ..., Ingo Molnar, (Sat Sep 6, 9:17 am)
[PATCH] Cleanup to make remove_memory() arch neutral, Badari Pulavarty, (Mon Sep 8, 2:52 pm)
[PATCH] x86: add memory hotremove config option, Badari Pulavarty, (Mon Sep 8, 2:56 pm)
Re: [PATCH] Cleanup to make remove_memory() arch neutral, Badari Pulavarty, (Tue Sep 9, 8:12 am)