From: David Rientjes <rientjes@google.com>
To: Alex Chiang <achiang@hp.com>
Cc: akpm@linux-foundation.org, Randy Dunlap <randy.dunlap@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH 5/5] Documentation: ABI: document /sys/devices/system/cpu/
Date: Mon, 19 Oct 2009 20:28:03 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0910192022460.25264@chino.kir.corp.google.com> (raw)
In-Reply-To: <20091019213435.32729.81751.stgit@bob.kio>
On Mon, 19 Oct 2009, Alex Chiang wrote:
> diff --git a/Documentation/ABI/testing/sysfs-devices-cpu b/Documentation/ABI/testing/sysfs-devices-cpu
> new file mode 100644
> index 0000000..9070889
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-devices-cpu
Shouldn't this be called sysfs-devices-system-cpu?
I see what you're doing: /sys/devices/system/node/* files are contained in
sysfs-devices-memory, but I think it would be helpful to have a more
strict naming scheme so that the contents of a sysfs directory are
described by a file of the same name.
> @@ -0,0 +1,42 @@
> +What: /sys/devices/system/cpu/
> +Date: October 2009
> +Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
> +Description:
> + A collection of CPU attributes, including cache information,
> + topology, and frequency. It also contains a mechanism to
> + logically hotplug CPUs.
> +
> + The actual attributes present are architecture and
> + configuration dependent.
> +
> +
> +What: /sys/devices/system/cpu/$cpu/online
cpu# ?
> +Date: January 2006
> +Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
> +Description:
> + When CONFIG_HOTPLUG_CPU is enabled, allows the user to
> + discover and change the online state of a CPU. To discover
> + the state:
This is present even without CONFIG_HOTPLUG_CPU.
> +
> + cat /sys/devices/system/cpu/$cpu/online
> +
> + A value of 0 indicates the CPU is offline. A value of 1
> + indicates it is online. To change the state, echo the
> + desired new state into the file:
> +
> + echo [0|1] > /sys/devices/system/cpu/$cpu/online
> +
> + For more information, please read Documentation/cpu-hotplug.txt
> +
> +
> +What: /sys/devices/system/cpu/$cpu/node
> +Date: October 2009
> +Contact: Linux memory management mailing list <linux-mm@kvack.org>
> +Description:
> + When CONFIG_NUMA is enabled, a symbolic link that points
> + to the corresponding NUMA node directory.
> +
> + For example, the following symlink is created for cpu42
> + in NUMA node 2:
> +
> + /sys/devices/system/cpu/cpu42/node2 -> ../../node/node2
>
Would it be possible for you to document all entities in
/sys/devices/system/cpu/* in this new file (requiring a folding of
Documentation/ABI/testing/sysfs-devices-cache_disable into it)?
--
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:[~2009-10-20 3:28 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
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 [this message]
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.0910192022460.25264@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=randy.dunlap@oracle.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