From: Gary Hade <garyhade@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Gary Hade <garyhade@us.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
y-goto@jp.fujitsu.com, pbadari@us.ibm.com, mel@csn.ul.ie,
lcm@us.ibm.com, mingo@elte.hu, greg@kroah.com,
dave@linux.vnet.ibm.com, nish.aravamudan@gmail.com
Subject: Re: [PATCH 1/2] [REPOST] mm: show node to memory section relationship with symlinks in sysfs
Date: Fri, 10 Oct 2008 14:33:57 -0700 [thread overview]
Message-ID: <20081010213357.GD7369@us.ibm.com> (raw)
In-Reply-To: <20081010124239.f92b5568.akpm@linux-foundation.org>
On Fri, Oct 10, 2008 at 12:42:39PM -0700, Andrew Morton wrote:
> On Thu, 9 Oct 2008 12:21:15 -0700
> Gary Hade <garyhade@us.ibm.com> wrote:
>
> > Show node to memory section relationship with symlinks in sysfs
> >
> > Add /sys/devices/system/node/nodeX/memoryY symlinks for all
> > the memory sections located on nodeX. For example:
> > /sys/devices/system/node/node1/memory135 -> ../../memory/memory135
> > indicates that memory section 135 resides on node1.
>
> I'm not seeing here a description of why the kernel needs this feature.
> Why is it useful? How will it be used? What value does it have to
> our users?
Sorry, I should have included that. In our case, it is another
small step towards eventual total node removal. We will need to
know which memory sections to offline for whatever node is targeted
for removal. However, I suspect that exposing the node to section
information to user-level could be useful for other purposes.
For example, I have been thinking that using memory hotremove
functionality to modify the amount of available memory on specific
nodes without having to physically add/remove DIMMs might be useful
to those that test application or benchmark performance on a
multi-node system in various memory configurations.
Gary
--
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503 IBM T/L: 775-4503
garyhade@us.ibm.com
http://www.ibm.com/linux/ltc
--
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>
next prev parent reply other threads:[~2008-10-10 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 19:21 Gary Hade
2008-10-10 10:55 ` Yasunori Goto
2008-10-10 19:42 ` Andrew Morton
2008-10-10 21:33 ` Gary Hade [this message]
2008-10-10 21:59 ` Andrew Morton
2008-10-10 23:18 ` Gary Hade
2008-10-10 23:32 ` Andrew Morton
2008-10-13 16:34 ` Gary Hade
2008-10-13 16:40 ` Dave Hansen
2008-10-14 11:54 ` Yasunori Goto
2008-10-14 21:06 ` Gary Hade
2008-10-15 10:37 ` Yasunori Goto
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=20081010213357.GD7369@us.ibm.com \
--to=garyhade@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=greg@kroah.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=nish.aravamudan@gmail.com \
--cc=pbadari@us.ibm.com \
--cc=y-goto@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox