linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Gary Hade <garyhade@us.ibm.com>,
	linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Yasunori Goto <y-goto@jp.fujitsu.com>, Mel Gorman <mel@csn.ul.ie>,
	Chris McDermott <lcm@us.ibm.com>
Subject: Re: [PATCH] Show memory section to node relationship in sysfs
Date: Thu, 04 Sep 2008 16:31:00 -0700	[thread overview]
Message-ID: <48C06FB4.1040100@us.ibm.com> (raw)
In-Reply-To: <29495f1d0809041514y8cb4764h11aacd3a78cec58d@mail.gmail.com>

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 ?
> Dunno, the latter probably should be a separate patch, but does seem
> more like the sysfs behavior (and the number (node or memory section)
> should be easily obtained from the symlinks via readlink, as opposed
> to cat with the current patch?).
>
> Thanks,
> Nish
>   

Thanks,
Badari

--
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>

  reply	other threads:[~2008-09-04 23:31 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 [this message]
2008-09-05  2:07     ` Gary Hade
2008-09-05  2:29       ` Yasunori Goto
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=48C06FB4.1040100@us.ibm.com \
    --to=pbadari@us.ibm.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=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