public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [Trivial Patch] cpusets docs - mention notify_on_release
@ 2005-03-27  6:52 Paul Jackson
  0 siblings, 0 replies; only message in thread
From: Paul Jackson @ 2005-03-27  6:52 UTC (permalink / raw)
  To: trivial; +Cc: Simon Derr, Paul Jackson, linux-kernel

Provide (minimal) documentation of the cpusets notify_on_release file.

Signed-off-by: Paul Jackson <pj@sgi.com>

Index: 2.6.12-pj/Documentation/cpusets.txt
===================================================================
--- 2.6.12-pj.orig/Documentation/cpusets.txt	2005-03-26 19:57:27.000000000 -0800
+++ 2.6.12-pj/Documentation/cpusets.txt	2005-03-26 19:58:43.000000000 -0800
@@ -166,6 +166,7 @@ containing the following files describin
  - mems: list of Memory Nodes in that cpuset
  - cpu_exclusive flag: is cpu placement exclusive?
  - mem_exclusive flag: is memory placement exclusive?
+ - notify_on_release: call /sbin/cpuset_release_agent on exit if set
  - tasks: list of tasks (by pid) attached to that cpuset
 
 New cpusets are created using the mkdir system call or shell
@@ -333,7 +334,7 @@ Now you want to do something with this c
 
 In this directory you can find several files:
 # ls
-cpus  cpu_exclusive  mems  mem_exclusive  tasks
+cpus  cpu_exclusive  mems  mem_exclusive  notify_on_release  tasks
 
 Reading them will give you information about the state of this cpuset:
 the CPUs and Memory Nodes it can use, the processes that are using

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-03-27  6:52 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-27  6:52 [Trivial Patch] cpusets docs - mention notify_on_release Paul Jackson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox