diff --git a/doc/cset-shield.1 b/doc/cset-shield.1 index 85901f5..8bbb5d8 100644 --- a/doc/cset-shield.1 +++ b/doc/cset-shield.1 @@ -1,13 +1,22 @@ '\" t .\" Title: cset-shield -.\" Author: [see the "AUTHOR" section] -.\" Generator: DocBook XSL Stylesheets v1.75.2 -.\" Date: 06/09/2011 -.\" Manual: [FIXME: manual] -.\" Source: [FIXME: source] +.\" Author: Alex Tsariounov +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: June 2011 +.\" Manual: \ \& +.\" Source: \ \& 1.5.6 .\" Language: English .\" -.TH "CSET\-SHIELD" "1" "06/09/2011" "[FIXME: source]" "[FIXME: manual]" +.TH "CSET\-SHIELD" "1" "June 2011" "\ \& 1\&.5\&.6" "\ \&" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- @@ -208,7 +217,7 @@ The above command moves all processes and threads with PID or TID in the range 5 The range of PIDs or TIDs does not need to have every position populated\&. In other words, for the example above, if there is only one process, say PID 57, in the range of 50\-65, then only that process will be moved\&. .sp .5v .RE -The \-\-unshield (or \-u) subcommand will remove the specified processes or threads from the shielded cpuset and move them into the unshielded (or system) cpuset\&. This command is also used in conjuction with a \-p/\-\-pid option that specifies a PIDSPEC argument, the same as for the \-\-shield subcommand\&. +The \-\-unshield (or \-u) subcommand will remove the specified processes or threads from the shielded cpuset and move them into the unshielded (or system) cpuset\&. This command is also used in conjunction with a \-p/\-\-pid option that specifies a PIDSPEC argument, the same as for the \-\-shield subcommand\&. Both the \-\-shield and the \-\-unshield commands will also finally output the number of tasks running in the shield and out of the shield if you do not specify a PIDSPEC with \-\-pid\&. By specifying also a \-\-verbose in addition, then you will get a listing of every task that is running in either the shield or out of the shield\&. @@ -252,4 +261,9 @@ cset(1), cset\-set(1), cset\-proc(1) taskset(1), chrt(1) /usr/src/linux/Documentation/cpusets\&.txt - +.SH "AUTHOR" +.PP +\fBAlex Tsariounov\fR <\&alext@novell\&.com\&> +.RS 4 +Author. +.RE diff --git a/doc/cset-shield.html b/doc/cset-shield.html index 93e799a..05056ff 100644 --- a/doc/cset-shield.html +++ b/doc/cset-shield.html @@ -2,15 +2,25 @@ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> - - + + cset-shield(1) + - + +
+

SYNOPSIS

-
cset [cset options] shield [shield options] [args] +
cset [cset options] shield [shield options] [args]
 cset shield --help
 cset shield
 cset shield --cpu 1-7
@@ -426,10 +757,12 @@ cset-shield(1) Manual Page
 cset shield --unshield --pid 6000-8500
 cset shield --kthread=off
 cset shield --kthread=on
-cset shield --shield bash
-
+cset shield --shield bash +
+
+

OPTIONS

@@ -550,6 +883,8 @@ cset-shield(1) Manual Page
+
+

DESCRIPTION

This is a supercommand that creates basic cpu shielding. The @@ -588,7 +923,7 @@ is running in initially when using the --shield subcommand. be under the shield (this means assigned to the user cpuset, all other cpus will be assigned to the system set).

For example:

-

# cset shield --cpu=1-3

+

# cset shield --cpu=1-3

On a 4-way machine, this command will dedicate the first processor, CPU0, for the system set (unshielded) and the last three processors, CPU1, CPU2, CPU3, for the user set (shielded).

@@ -601,7 +936,7 @@ cpuset.

unshielded and shielded sets respectively, or if those names are used already, then use the --sysset and --userset options.

For example:

-

# cset shield --sysset=free --userset=cage --cpu=2,3 --kthread=on

+

# cset shield --sysset=free --userset=cage --cpu=2,3 --kthread=on

The above command will use the name "free" for the unshielded system cpuset, the name "cage" for the shielded user cpuset, initialize these cpusets and dedicate CPU0 and CPU1 to the "free" @@ -626,7 +961,7 @@ subcommand and the --pid option.

traditional "--" marker to separate cset’s options from your command’s options.

For example:

-

# cset shield --exec — ls -l

+

# cset shield --exec — ls -l

This command will execute "ls -l" inside the shield.

The PIDSPEC argument taken for the --pid (or -p) option is a comma separated list of PIDs or TIDs. The list can also include @@ -634,10 +969,10 @@ brackets of PIDs or TIDs that are inclusive of the endpoints.

For example:

-
1,2,5               Means processes 1, 2 and 5
-1,2,600-700         Means processes 1, 2 and from 600 to 700
+
1,2,5               Means processes 1, 2 and 5
+1,2,600-700         Means processes 1, 2 and from 600 to 700
-

# cset shield --shield --pid=50-65

+

# cset shield --shield --pid=50-65

The above command moves all processes and threads with PID or TID in the range 50-65 inclusive, from the system cpuset into the shielded user cpuset. If they are running in the root cpuset, @@ -657,7 +992,7 @@ then only that process will be moved.

The --unshield (or -u) subcommand will remove the specified processes or threads from the shielded cpuset and move them into the unshielded (or system) cpuset. This command is also used in -conjuction with a -p/--pid option that specifies a PIDSPEC +conjunction with a -p/--pid option that specifies a PIDSPEC argument, the same as for the --shield subcommand.

Both the --shield and the --unshield commands will also finally output the number of tasks running in the shield and out of the @@ -674,7 +1009,7 @@ initialized.

For example if the original shield contained CPU0 and CPU1 in the system set and CPU2 and CPU3 in the user set, if you then issue the following command:

-

# cset shield --cpu=1,2,3

+

# cset shield --cpu=1,2,3

then that command will move CPU1 into the shielded "user" cpuset. Any processes or threads that were running on CPU1 that belonged to the unshielded "system" cpuset are migrated to CPU0 by the @@ -700,18 +1035,26 @@ and proc) directly.

+
+

LICENSE

Cpuset is licensed under the GNU GPL V2 only.

+
+

COPYRIGHT

Copyright (c) 2008-2011 Novell Inc.

+
+

AUTHOR

Written by Alex Tsariounov <alext@novell.com>.

+
+

SEE ALSO

cset(1), cset-set(1), cset-proc(1)

@@ -719,10 +1062,13 @@ and proc) directly.

taskset(1), chrt(1)

/usr/src/linux/Documentation/cpusets.txt

+
+ +
diff --git a/doc/cset-shield.txt b/doc/cset-shield.txt index d2e75b1..3bc6f06 100644 --- a/doc/cset-shield.txt +++ b/doc/cset-shield.txt @@ -180,7 +180,7 @@ then only that process will be moved. The --unshield (or -u) subcommand will remove the specified processes or threads from the shielded cpuset and move them into the unshielded (or system) cpuset. This command is also used in -conjuction with a -p/--pid option that specifies a PIDSPEC +conjunction with a -p/--pid option that specifies a PIDSPEC argument, the same as for the --shield subcommand. Both the --shield and the --unshield commands will also finally