From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
Nish Aravamudan <nish.aravamudan@gmail.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>, Chris McDermott <lcm@us.ibm.com>
Subject: Re: [PATCH] Show memory section to node relationship in sysfs
Date: Fri, 05 Sep 2008 11:29:19 +0900 [thread overview]
Message-ID: <20080905112632.6756.E1E9C6FF@jp.fujitsu.com> (raw)
In-Reply-To: <20080905020729.GG26795@us.ibm.com>
> On Thu, Sep 04, 2008 at 04:31:00PM -0700, Badari Pulavarty wrote:
> > Nish Aravamudan wrote:
> >> On 9/4/08, Gary Hade <garyhade@us.ibm.com> wrote:
> >>
> >>> Show memory section to node relationship in sysfs
> >>>
> >>> Add /sys/devices/system/memory/memoryX/node files to show
> >>> the node on which each memory section resides.
> >>>
> >>
> >> I think this patch needs an additional bit for Documentation/ABI
> >> (might be other parts of /sys/devices/system/memory missing from
> >> there).
> >>
> >>
> > Yes. I added Documentation/ABI for "removable". We should update it for
> > this too.
> >> Also, I wonder if it might not make more sense to use a symlink here? That is
> >>
> >> /sys/devices/system/memory/memoryX/node -> /sys/devices/system/node/nodeY ?
> >>
> >>
> > Makes sense. Since we already have "node/nodeY", we might as well make
> > use of it
> > instead of duplicating it.
> >> And then we could, potentially, have symlinks returning from the node
> >> side to indicate all memory sections on that node (might be handy for
> >> node offline?):
> >>
> >> /sys/devices/system/node/nodeX/memory1 -> /sys/devices/system/memory/memoryY
> >> /sys/devices/system/node/nodeX/memory2 -> /sys/devices/system/memory/memoryZ
> >>
> >>
> > I don't think we need both. Gary wants to do "node removal/offline" and
> > wants
> > to find out all the memory sections that belong to nodeX. May be this is a
> > a better interface. This way, we can quickly get through all the memory
> > sections without looking at all the sections. Gary ?
>
> Yes, either way would work fine but I think symlinks in the
> /sys/devices/system/node/nodeX directories would make the
> script or program driven memory section offlining complete
> a little more quickly. However, if we do this we might want to
> make the symlink names to match the memory section directory names.
> /sys/devices/system/node/nodeX/memoryY -> /sys/devices/system/memory/memoryY
> /sys/devices/system/node/nodeX/memoryZ -> /sys/devices/system/memory/memoryZ
Agree. I think this is better way.
Thanks.
--
Yasunori Goto
--
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-09-05 2:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 20:22 Gary Hade
2008-09-04 22:14 ` Nish Aravamudan
2008-09-04 23:31 ` Badari Pulavarty
2008-09-05 2:07 ` Gary Hade
2008-09-05 2:29 ` Yasunori Goto [this message]
2008-09-04 22:15 ` Dave Hansen
2008-09-05 0:40 ` Greg KH
2008-09-05 1:15 ` Gary Hade
2008-09-05 1:21 ` Greg KH
2008-09-05 3:18 ` Gary Hade
2008-09-05 1:00 ` Gary Hade
2008-09-05 17:42 ` Dave Hansen
2008-09-05 17:46 ` Gary Hade
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=20080905112632.6756.E1E9C6FF@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=garyhade@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=nish.aravamudan@gmail.com \
--cc=pbadari@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox