From: Dave Hansen <dave.hansen@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Nivedita Singhvi <niv@us.ibm.com>,
Michael J Wolf <mjwolf@us.ibm.com>,
linux-kernel@vger.kernel.org, Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] drivers: base: new memory config sysfs driver for large memory systems
Date: Thu, 01 Aug 2013 15:13:03 -0700 [thread overview]
Message-ID: <51FADD6F.3040804@linux.intel.com> (raw)
In-Reply-To: <20130801205724.GA13585@kroah.com>
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, 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@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Nivedita Singhvi <niv@us.ibm.com>,
Michael J Wolf <mjwolf@us.ibm.com>,
linux-kernel@vger.kernel.org, Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] drivers: base: new memory config sysfs driver for large memory systems
Date: Thu, 01 Aug 2013 15:13:03 -0700 [thread overview]
Message-ID: <51FADD6F.3040804@linux.intel.com> (raw)
In-Reply-To: <20130801205724.GA13585@kroah.com>
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?
next prev parent reply other threads:[~2013-08-01 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1374786680-26197-1-git-send-email-sjenning@linux.vnet.ibm.com>
2013-07-25 23:38 ` [PATCH] drivers: base: new memory config sysfs driver for large memory systems Greg Kroah-Hartman
2013-07-26 14:33 ` Seth Jennings
2013-08-01 20:57 ` Greg Kroah-Hartman
2013-07-25 23:40 ` Greg Kroah-Hartman
2013-07-26 14:42 ` Seth Jennings
2013-08-01 20:57 ` Greg Kroah-Hartman
2013-08-01 22:13 ` Dave Hansen [this message]
2013-08-01 22:13 ` Dave Hansen
2013-08-02 15:50 ` Seth Jennings
2013-08-02 15:50 ` Seth Jennings
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=51FADD6F.3040804@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjwolf@us.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=niv@us.ibm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sjenning@linux.vnet.ibm.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.