Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750803AbWBIVjf (ORCPT ); Thu, 9 Feb 2006 16:39:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750806AbWBIVje (ORCPT ); Thu, 9 Feb 2006 16:39:34 -0500 Received: from e31.co.us.ibm.com ([32.97.110.149]:62857 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S1750803AbWBIVjd (ORCPT ); Thu, 9 Feb 2006 16:39:33 -0500 Message-ID: <43EBB68A.3040105@austin.ibm.com> Date: Thu, 09 Feb 2006 15:39:22 -0600 From: Joel Schopp User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: "Luck, Tony" CC: Yasunori Goto , Andi Kleen , "Brown, Len" , "Tolentino, Matthew E" , "S, Naveen B" , Bjorn Helgaas , ACPI-ML , Linux Kernel ML , linux-ia64@vger.kernel.org, x86-64 Discuss , Linux Hotplug Memory Support Subject: Re: [Lhms-devel] [RFC:PATCH(000/003)] Memory add to onlined node. (ver. 2) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 985 Lines: 25 >> - if the node is already online.- If the node is offline, >> (It means new node is comming!) then the memory will belongs >> to node 0 yet. > > What is the long term plan to address this? Can you make sure > that the new node is always brought online before you get to > this code? Or will you have to bring the node online in the > middle of the memory hot-add code? > > Presumably there is a similar issue with hot add cpu. > Yes, cpu hot add has the same issue. It's really a performance issue, not a functional one so you haven't seen people beating down the doors to fix it. Technically there isn't anything but manpower standing in the way of doing it. But it is a good amount of work for the little it gains. -Joel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/