As I found out recently, memory hotplug is disabled in f17 and f18 kernels (but not in f16).
Can anybody please recall the reason for that? The commit doing that is not particularly enlightening:
commit 2ee9f1482920f6d831eb6d70458bd0988394982b Author: Dave Jones davej@redhat.com Date: Fri Jan 13 17:33:51 2012 -0500
Disable memory hotplug on x86-64
I'd like to propose to re-enable it but I'm trying to figure out why it was disabled in the first place.
Thanks, Roman.
On Tue, Nov 20, 2012 at 05:43:16PM +0400, Roman Kagan wrote:
As I found out recently, memory hotplug is disabled in f17 and f18 kernels (but not in f16).
Can anybody please recall the reason for that? The commit doing that is not particularly enlightening:
commit 2ee9f1482920f6d831eb6d70458bd0988394982b Author: Dave Jones davej@redhat.com Date: Fri Jan 13 17:33:51 2012 -0500
Disable memory hotplug on x86-64
I'd like to propose to re-enable it but I'm trying to figure out why it was disabled in the first place.
That is a pretty terrible changelog. And I don't recall my reasoning tbh. It was around the time of F17 development where we disabled a lot of stuff, so it may have just been overly optimistic that it was unused.
Unless someone else has a good reason not to, we can reenable it. (How well it works however is unknown to me)
Dave
2012/11/20 Dave Jones davej@redhat.com:
On Tue, Nov 20, 2012 at 05:43:16PM +0400, Roman Kagan wrote:
As I found out recently, memory hotplug is disabled in f17 and f18 kernels (but not in f16).
Unless someone else has a good reason not to, we can reenable it. (How well it works however is unknown to me)
Since f16 has it enabled and isn't known to have massive problems due to that, it's probably safe to reenable it in f17+.
I'll build a memhotplug-enabled kernel and test it lightly in a virtual machine with f17, and let you know the outcome.
Roman.
kernel@lists.fedoraproject.org