From: Dave Hansen <dave.hansen@intel.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Dave Hansen <dave@sr71.net>, Michal Hocko <mhocko@suse.cz>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kamezawa.hiroyuki@gmail.com" <kamezawa.hiroyuki@gmail.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"yinghan@google.com" <yinghan@google.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"kay@vrfy.org" <kay@vrfy.org>
Subject: Re: [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks
Date: Wed, 24 Jul 2013 14:02:32 -0700 [thread overview]
Message-ID: <51F040E8.1030507@intel.com> (raw)
In-Reply-To: <d1f80c05986b439cbeef12bcd595b264@BLUPR03MB050.namprd03.prod.outlook.com>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@intel.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Dave Hansen <dave@sr71.net>, Michal Hocko <mhocko@suse.cz>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kamezawa.hiroyuki@gmail.com" <kamezawa.hiroyuki@gmail.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"yinghan@google.com" <yinghan@google.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"kay@vrfy.org" <kay@vrfy.org>
Subject: Re: [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks
Date: Wed, 24 Jul 2013 14:02:32 -0700 [thread overview]
Message-ID: <51F040E8.1030507@intel.com> (raw)
In-Reply-To: <d1f80c05986b439cbeef12bcd595b264@BLUPR03MB050.namprd03.prod.outlook.com>
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.
next prev parent reply other threads:[~2013-07-24 21:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 19:23 [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks K. Y. Srinivasan
2013-07-19 19:23 ` K. Y. Srinivasan
2013-07-22 3:16 ` Jason Wang
2013-07-22 3:16 ` Jason Wang
2013-07-22 12:37 ` Michal Hocko
2013-07-22 12:37 ` Michal Hocko
2013-07-23 14:52 ` KY Srinivasan
2013-07-23 14:52 ` KY Srinivasan
2013-07-23 15:09 ` Michal Hocko
2013-07-23 15:09 ` Michal Hocko
2013-07-23 15:50 ` KY Srinivasan
2013-07-23 15:50 ` KY Srinivasan
2013-07-23 15:28 ` Dave Hansen
2013-07-23 15:28 ` Dave Hansen
2013-07-23 15:54 ` KY Srinivasan
2013-07-23 15:54 ` KY Srinivasan
2013-07-23 16:00 ` Dave Hansen
2013-07-23 16:00 ` Dave Hansen
2013-07-23 17:21 ` KY Srinivasan
2013-07-23 17:21 ` KY Srinivasan
2013-07-24 16:43 ` Dave Hansen
2013-07-24 16:43 ` Dave Hansen
2013-07-24 19:45 ` KY Srinivasan
2013-07-24 19:45 ` KY Srinivasan
2013-07-24 21:02 ` Dave Hansen [this message]
2013-07-24 21:02 ` Dave Hansen
2013-07-25 7:57 ` Michal Hocko
2013-07-25 7:57 ` Michal Hocko
2013-07-25 11:14 ` KY Srinivasan
2013-07-25 11:14 ` KY Srinivasan
2013-07-25 15:03 ` Dave Hansen
2013-07-25 15:03 ` Dave Hansen
2013-07-25 15:15 ` Kay Sievers
2013-07-25 15:15 ` Kay Sievers
2013-07-25 16:35 ` Dave Hansen
2013-07-25 16:35 ` Dave Hansen
2013-07-25 15:49 ` KY Srinivasan
2013-07-25 15:49 ` KY Srinivasan
2013-07-23 16:01 ` Greg KH
2013-07-23 16:01 ` Greg KH
2013-07-23 16:54 ` KY Srinivasan
2013-07-23 16:54 ` KY Srinivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F040E8.1030507@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=apw@canonical.com \
--cc=dave@sr71.net \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=jasowang@redhat.com \
--cc=kamezawa.hiroyuki@gmail.com \
--cc=kay@vrfy.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=olaf@aepfle.de \
--cc=yinghan@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.