lkml.org 
[lkml]   [2013]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [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?


\
 
 \ /
  Last update: 2013-08-02 00:41    [W:0.036 / U:0.500 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site