From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Date: Thu, 13 May 2004 06:45:38 +0000 Subject: Re: Node Hotplug Support Message-Id: <1084430738.3189.1.camel@nighthawk> List-Id: References: <20040508003904.63395ca7.tokunaga.keiich@jp.fujitsu.com> <1083944945.23559.1.camel@nighthawk> <20040510104725.7c9231ee.tokunaga.keiich@jp.fujitsu.com> <1084167941.28602.478.camel@nighthawk> <20040513102751.48c61d48.tokunaga.keiich@jp.fujitsu.com> <1084413887.974.7.camel@nighthawk> <20040513153505.21c5fc15.tokunaga.keiich@jp.fujitsu.com> In-Reply-To: <20040513153505.21c5fc15.tokunaga.keiich@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Keiichiro Tokunaga Cc: Linux Kernel Mailing List , hotplug devel , lhns-devel@lists.sourceforge.net On Wed, 2004-05-12 at 23:35, Keiichiro Tokunaga wrote: > LHNS is focusing on "container device hotplug". Container device > could contain CPUs, memory, and/or IO devices. Container device > could contain only IO devices. In this case, LHNS cannot use > $NODED/control/online (NUMA stuff) for the container device. So, why not expose your containers in the same way that all of the other NUMA node information is exported? What makes your NUMA containers different from all of the other flavors of NUMA implementations in Linux? > By the way, what happen when you issue > "echo 0 > $NODEDIR/control/online"? Can you detach it > from the system after echo-ing? Well, since it doesn't exist yet... Sure :) -- Dave ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel