Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753889Ab3GXVDB (ORCPT ); Wed, 24 Jul 2013 17:03:01 -0400 Received: from mga09.intel.com ([134.134.136.24]:65257 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753350Ab3GXVC7 (ORCPT ); Wed, 24 Jul 2013 17:02:59 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,737,1367996400"; d="scan'208";a="370438191" Message-ID: <51F040E8.1030507@intel.com> Date: Wed, 24 Jul 2013 14:02:32 -0700 From: Dave Hansen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 To: KY Srinivasan CC: Dave Hansen , Michal Hocko , "gregkh@linuxfoundation.org" , "linux-kernel@vger.kernel.org" , "devel@linuxdriverproject.org" , "olaf@aepfle.de" , "apw@canonical.com" , "andi@firstfloor.org" , "akpm@linux-foundation.org" , "linux-mm@kvack.org" , "kamezawa.hiroyuki@gmail.com" , "hannes@cmpxchg.org" , "yinghan@google.com" , "jasowang@redhat.com" , "kay@vrfy.org" Subject: Re: [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks References: <1374261785-1615-1-git-send-email-kys@microsoft.com> <20130722123716.GB24400@dhcp22.suse.cz> <51EEA11D.4030007@intel.com> <3318be0a96cb4d05838d76dc9d088cc0@SN2PR03MB061.namprd03.prod.outlook.com> <51EEA89F.9070309@intel.com> <9f351a549e76483d9148f87535567ea0@SN2PR03MB061.namprd03.prod.outlook.com> <51F00415.8070104@sr71.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 897 Lines: 17 On 07/24/2013 12:45 PM, KY Srinivasan wrote: > All I am saying is that I see two classes of failures: (a) Our > inability to allocate memory to manage the memory that is being hot added > and (b) Our inability to bring the hot added memory online within a reasonable > amount of time. I am not sure the cause for (b) and I was just speculating that > this could be memory related. What is interesting is that I have seen failure related > to our inability to online the memory after having succeeded in hot adding the > memory. I think we should hold off on this patch and other like it until we've been sufficiently able to explain how (b) happens. -- 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/