[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51FADD6F.3040804@linux.intel.com>
Date: Thu, 01 Aug 2013 15:13:03 -0700
From: Dave Hansen <dave.hansen@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Seth Jennings <sjenning@...ux.vnet.ibm.com>,
Nathan Fontenot <nfont@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Nivedita Singhvi <niv@...ibm.com>,
Michael J Wolf <mjwolf@...ibm.com>,
linux-kernel@...r.kernel.org, Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH] drivers: base: new memory config sysfs driver for large
memory systems
On 08/01/2013 01:57 PM, Greg Kroah-Hartman wrote:
>> > "memory" is the name used by the current sysfs memory layout code in
>> > drivers/base/memory.c. So it can't be the same unless we are going to
>> > create a toggle a boot time to select between the models, which is
>> > something I am looking to add if this code/design is acceptable to
>> > people.
> I know it can't be the same, but this is like "memory_v2" or something,
> right? I suggest you make it an either/or option, given that you feel
> the existing layout just will not work properly for you.
If there are existing tools or applications that look for memory hotplug
events, how does this interact with those? I know you guys have control
over the ppc software that actually performs the probe/online
operations, but what about other apps?
I also don't seem to see the original post to LKML. Did you send
privately to Greg, then he cc'd LKML on his reply?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists