All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	Ingo Molnar <mingo@elte.hu>, Gary Hade <garyhade@us.ibm.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] mm: add numa node symlink for memory section in sysfs
Date: Wed, 21 Oct 2009 12:27:11 -0600	[thread overview]
Message-ID: <20091021182711.GI23948@ldl.fc.hp.com> (raw)
In-Reply-To: <c18f2c2738f6a584b431324b38f21970.squirrel@webmail-b.css.fujitsu.com>

* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>:
> Alex Chiang wrote:
> > Commit c04fc586c (mm: show node to memory section relationship with
> > symlinks in sysfs) created symlinks from nodes to memory sections, e.g.
> >
> > /sys/devices/system/node/node1/memory135 -> ../../memory/memory135
> >
> > If you're examining the memory section though and are wondering what
> > node it might belong to, you can find it by grovelling around in
> > sysfs, but it's a little cumbersome.
> >
> > Add a reverse symlink for each memory section that points back to the
> > node to which it belongs.
> >
> > Cc: Gary Hade <garyhade@us.ibm.com>
> > Cc: Badari Pulavarty <pbadari@us.ibm.com>
> > Cc: Ingo Molnar <mingo@elte.hu>
> > Signed-off-by: Alex Chiang <achiang@hp.com>
> 
> 2 yeas ago, I wanted to add this symlink. But don't...because
> some vendor's host has no 1-to-1 relationship between a memsection
> and a node. (I don't remember precisely, sorry....s390?)

Hm, ok. I'll cc the s390 folks in the next version of this series.

Thanks for the pointer.

/ac


WARNING: multiple messages have this Message-ID (diff)
From: Alex Chiang <achiang@hp.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	Ingo Molnar <mingo@elte.hu>, Gary Hade <garyhade@us.ibm.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] mm: add numa node symlink for memory section in sysfs
Date: Wed, 21 Oct 2009 12:27:11 -0600	[thread overview]
Message-ID: <20091021182711.GI23948@ldl.fc.hp.com> (raw)
In-Reply-To: <c18f2c2738f6a584b431324b38f21970.squirrel@webmail-b.css.fujitsu.com>

* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>:
> Alex Chiang wrote:
> > Commit c04fc586c (mm: show node to memory section relationship with
> > symlinks in sysfs) created symlinks from nodes to memory sections, e.g.
> >
> > /sys/devices/system/node/node1/memory135 -> ../../memory/memory135
> >
> > If you're examining the memory section though and are wondering what
> > node it might belong to, you can find it by grovelling around in
> > sysfs, but it's a little cumbersome.
> >
> > Add a reverse symlink for each memory section that points back to the
> > node to which it belongs.
> >
> > Cc: Gary Hade <garyhade@us.ibm.com>
> > Cc: Badari Pulavarty <pbadari@us.ibm.com>
> > Cc: Ingo Molnar <mingo@elte.hu>
> > Signed-off-by: Alex Chiang <achiang@hp.com>
> 
> 2 yeas ago, I wanted to add this symlink. But don't...because
> some vendor's host has no 1-to-1 relationship between a memsection
> and a node. (I don't remember precisely, sorry....s390?)

Hm, ok. I'll cc the s390 folks in the next version of this series.

Thanks for the pointer.

/ac

--
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:[~2009-10-21 18:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 21:34 [PATCH 0/5] mm: modest useability enhancements for node sysfs attrs Alex Chiang
2009-10-19 21:34 ` Alex Chiang
2009-10-19 21:34 ` [PATCH 1/5] mm: add numa node symlink for memory section in sysfs Alex Chiang
2009-10-19 21:34   ` Alex Chiang
2009-10-20 11:55   ` KAMEZAWA Hiroyuki
2009-10-20 11:55     ` KAMEZAWA Hiroyuki
2009-10-21 18:27     ` Alex Chiang [this message]
2009-10-21 18:27       ` Alex Chiang
2009-10-19 21:34 ` [PATCH 2/5] mm: refactor register_cpu_under_node() Alex Chiang
2009-10-19 21:34   ` Alex Chiang
2009-10-19 21:34 ` [PATCH 3/5] mm: refactor unregister_cpu_under_node() Alex Chiang
2009-10-19 21:34   ` Alex Chiang
2009-10-19 21:34 ` [PATCH 4/5] mm: add numa node symlink for cpu devices in sysfs Alex Chiang
2009-10-19 21:34   ` Alex Chiang
2009-10-20  3:18   ` David Rientjes
2009-10-20  3:18     ` David Rientjes
2009-10-20 20:41     ` Alex Chiang
2009-10-20 20:41       ` Alex Chiang
2009-10-20 21:09       ` David Rientjes
2009-10-20 21:09         ` David Rientjes
2009-10-21 19:30         ` Alex Chiang
2009-10-21 19:30           ` Alex Chiang
2009-10-19 21:34 ` [PATCH 5/5] Documentation: ABI: document /sys/devices/system/cpu/ Alex Chiang
2009-10-19 21:34   ` Alex Chiang
2009-10-20  3:28   ` David Rientjes
2009-10-20  3:28     ` David Rientjes
2009-10-20 20:47     ` Alex Chiang
2009-10-20 20:47       ` Alex Chiang
2009-10-20 21:13       ` David Rientjes
2009-10-20 21:13         ` David Rientjes

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=20091021182711.GI23948@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=garyhade@us.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --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 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.