Re: [PATCH] memory hotplug disable boot option
From: KAMEZAWA Hiroyuki
Date: Wed Jun 30 2010 - 20:36:41 EST
On Wed, 30 Jun 2010 08:47:55 -0700
Greg KH <gregkh@xxxxxxx> wrote:
> > and adding a scalable interface for large scale machines ?
> > I'd like to consider something..
> Dynamically changing the layout on big memory boxes makes sense to me,
> how about you?
like this ?
Considering briefly, how about this compact layout ?
list, hide, show, memoryX...
list: // show available memory index list.
0 1 2 ....10000...
show: //an interface to enable the interface.
#echo INDEX > memory_index
will create memoryINDEX diretory.
hide: //an interface to hide the interface.
#echo INDEX > memory_hide
will remove memoryINDEX sysfs directory.
In compact mode, all memoryX interface are hidden at boot.
In full mode, all memoryX interaface are shown.
The Boot option just affects status at boot. If users want, he can make
all memory sysfs in shown state.
At hot-add event (via acpi) or probe-event, newly created memory section
should be start from "shown" mode. hotplug scirpt can hide it after online.
At hot-remove, the users has to offline memory before hotplug. He'll has
to do check list and show interface.
I think this change is not very difficult technically but can this kind of
interface be allowed ?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/