linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Alex Chiang <achiang@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] mm: add numa node symlink for cpu devices in sysfs
Date: Tue, 20 Oct 2009 14:09:45 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.1.00.0910201407190.27248@chino.kir.corp.google.com> (raw)
In-Reply-To: <20091020204136.GB23675@ldl.fc.hp.com>

On Tue, 20 Oct 2009, Alex Chiang wrote:

> * David Rientjes <rientjes@google.com>:
> > On Mon, 19 Oct 2009, Alex Chiang wrote:
> > 
> > > You can discover which CPUs belong to a NUMA node by examining
> > > /sys/devices/system/node/$node/
> > > 
> > 
> > You mean /sys/devices/system/node/node# ?
> 
> Hm, in PCI land, I've been using $foo to indicate a variable in
> documentation I've written, but I can certainly use foo# if
> that's the preferred style.
> 

I'm referring to the directories in /sys/devices/system/node/ being 
'node13' for example, and not '13' as your changelog indicates.

> > > However, it's not convenient to go in the other direction, when looking at
> > > /sys/devices/system/cpu/$cpu/
> > > 
> > 
> > .../cpu/cpu# ?
> > 

Same here.

> > The return values of register_cpu_under_node() and 
> > unregister_cpu_under_node() are always ignored, so it would probably be 
> > best to convert these to be void functions.  That doesn't mean you can 
> > simply ignore the result of the first sysfs_create_link(), though: the 
> > second should probably be suppressed if the first returns an error.
> > 
> 
> I didn't want to change too much in the patch. Changing the
> function signature seems a bit overeager, but if you have strong
> feelings, I can do so.
> 

It's entirely up to you if you want to change them to be void.  I thought 
it would be cleaner if the first patch in the series would convert them to 
void on the basis that the return value is never actually used and then 
the following patches simply return on error conditions.

--
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-20 21:09 UTC|newest]

Thread overview: 15+ 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 ` [PATCH 1/5] mm: add numa node symlink for memory section in sysfs Alex Chiang
2009-10-20 11:55   ` KAMEZAWA Hiroyuki
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 ` [PATCH 3/5] mm: refactor unregister_cpu_under_node() Alex Chiang
2009-10-19 21:34 ` [PATCH 4/5] mm: add numa node symlink for cpu devices in sysfs Alex Chiang
2009-10-20  3:18   ` David Rientjes
2009-10-20 20:41     ` Alex Chiang
2009-10-20 21:09       ` David Rientjes [this message]
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-20  3:28   ` David Rientjes
2009-10-20 20:47     ` Alex Chiang
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=alpine.DEB.1.00.0910201407190.27248@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=achiang@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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