You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
709 lines
17 KiB
HTML
709 lines
17 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
|
|
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
|
|
<meta name="generator" content="AsciiDoc 8.4.5" />
|
|
<title>cset-proc(1)</title>
|
|
<style type="text/css">
|
|
/* Debug borders */
|
|
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
|
|
/*
|
|
border: 1px solid red;
|
|
*/
|
|
}
|
|
|
|
body {
|
|
margin: 1em 5% 1em 5%;
|
|
}
|
|
|
|
a {
|
|
color: blue;
|
|
text-decoration: underline;
|
|
}
|
|
a:visited {
|
|
color: fuchsia;
|
|
}
|
|
|
|
em {
|
|
font-style: italic;
|
|
color: navy;
|
|
}
|
|
|
|
strong {
|
|
font-weight: bold;
|
|
color: #083194;
|
|
}
|
|
|
|
tt {
|
|
color: navy;
|
|
}
|
|
|
|
h1, h2, h3, h4, h5, h6 {
|
|
color: #527bbd;
|
|
font-family: sans-serif;
|
|
margin-top: 1.2em;
|
|
margin-bottom: 0.5em;
|
|
line-height: 1.3;
|
|
}
|
|
|
|
h1, h2, h3 {
|
|
border-bottom: 2px solid silver;
|
|
}
|
|
h2 {
|
|
padding-top: 0.5em;
|
|
}
|
|
h3 {
|
|
float: left;
|
|
}
|
|
h3 + * {
|
|
clear: left;
|
|
}
|
|
|
|
div.sectionbody {
|
|
font-family: serif;
|
|
margin-left: 0;
|
|
}
|
|
|
|
hr {
|
|
border: 1px solid silver;
|
|
}
|
|
|
|
p {
|
|
margin-top: 0.5em;
|
|
margin-bottom: 0.5em;
|
|
}
|
|
|
|
ul, ol, li > p {
|
|
margin-top: 0;
|
|
}
|
|
|
|
pre {
|
|
padding: 0;
|
|
margin: 0;
|
|
}
|
|
|
|
span#author {
|
|
color: #527bbd;
|
|
font-family: sans-serif;
|
|
font-weight: bold;
|
|
font-size: 1.1em;
|
|
}
|
|
span#email {
|
|
}
|
|
span#revnumber, span#revdate, span#revremark {
|
|
font-family: sans-serif;
|
|
}
|
|
|
|
div#footer {
|
|
font-family: sans-serif;
|
|
font-size: small;
|
|
border-top: 2px solid silver;
|
|
padding-top: 0.5em;
|
|
margin-top: 4.0em;
|
|
}
|
|
div#footer-text {
|
|
float: left;
|
|
padding-bottom: 0.5em;
|
|
}
|
|
div#footer-badges {
|
|
float: right;
|
|
padding-bottom: 0.5em;
|
|
}
|
|
|
|
div#preamble {
|
|
margin-top: 1.5em;
|
|
margin-bottom: 1.5em;
|
|
}
|
|
div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
|
|
div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
|
|
div.admonitionblock {
|
|
margin-top: 1.5em;
|
|
margin-bottom: 1.5em;
|
|
}
|
|
div.admonitionblock {
|
|
margin-top: 2.5em;
|
|
margin-bottom: 2.5em;
|
|
}
|
|
|
|
div.content { /* Block element content. */
|
|
padding: 0;
|
|
}
|
|
|
|
/* Block element titles. */
|
|
div.title, caption.title {
|
|
color: #527bbd;
|
|
font-family: sans-serif;
|
|
font-weight: bold;
|
|
text-align: left;
|
|
margin-top: 1.0em;
|
|
margin-bottom: 0.5em;
|
|
}
|
|
div.title + * {
|
|
margin-top: 0;
|
|
}
|
|
|
|
td div.title:first-child {
|
|
margin-top: 0.0em;
|
|
}
|
|
div.content div.title:first-child {
|
|
margin-top: 0.0em;
|
|
}
|
|
div.content + div.title {
|
|
margin-top: 0.0em;
|
|
}
|
|
|
|
div.sidebarblock > div.content {
|
|
background: #ffffee;
|
|
border: 1px solid silver;
|
|
padding: 0.5em;
|
|
}
|
|
|
|
div.listingblock > div.content {
|
|
border: 1px solid silver;
|
|
background: #f4f4f4;
|
|
padding: 0.5em;
|
|
}
|
|
|
|
div.quoteblock {
|
|
padding-left: 2.0em;
|
|
margin-right: 10%;
|
|
}
|
|
div.quoteblock > div.attribution {
|
|
padding-top: 0.5em;
|
|
text-align: right;
|
|
}
|
|
|
|
div.verseblock {
|
|
padding-left: 2.0em;
|
|
margin-right: 10%;
|
|
}
|
|
div.verseblock > div.content {
|
|
white-space: pre;
|
|
}
|
|
div.verseblock > div.attribution {
|
|
padding-top: 0.75em;
|
|
text-align: left;
|
|
}
|
|
/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
|
|
div.verseblock + div.attribution {
|
|
text-align: left;
|
|
}
|
|
|
|
div.admonitionblock .icon {
|
|
vertical-align: top;
|
|
font-size: 1.1em;
|
|
font-weight: bold;
|
|
text-decoration: underline;
|
|
color: #527bbd;
|
|
padding-right: 0.5em;
|
|
}
|
|
div.admonitionblock td.content {
|
|
padding-left: 0.5em;
|
|
border-left: 2px solid silver;
|
|
}
|
|
|
|
div.exampleblock > div.content {
|
|
border-left: 2px solid silver;
|
|
padding: 0.5em;
|
|
}
|
|
|
|
div.imageblock div.content { padding-left: 0; }
|
|
span.image img { border-style: none; }
|
|
a.image:visited { color: white; }
|
|
|
|
dl {
|
|
margin-top: 0.8em;
|
|
margin-bottom: 0.8em;
|
|
}
|
|
dt {
|
|
margin-top: 0.5em;
|
|
margin-bottom: 0;
|
|
font-style: normal;
|
|
color: navy;
|
|
}
|
|
dd > *:first-child {
|
|
margin-top: 0.1em;
|
|
}
|
|
|
|
ul, ol {
|
|
list-style-position: outside;
|
|
}
|
|
ol.arabic {
|
|
list-style-type: decimal;
|
|
}
|
|
ol.loweralpha {
|
|
list-style-type: lower-alpha;
|
|
}
|
|
ol.upperalpha {
|
|
list-style-type: upper-alpha;
|
|
}
|
|
ol.lowerroman {
|
|
list-style-type: lower-roman;
|
|
}
|
|
ol.upperroman {
|
|
list-style-type: upper-roman;
|
|
}
|
|
|
|
div.compact ul, div.compact ol,
|
|
div.compact p, div.compact p,
|
|
div.compact div, div.compact div {
|
|
margin-top: 0.1em;
|
|
margin-bottom: 0.1em;
|
|
}
|
|
|
|
div.tableblock > table {
|
|
border: 3px solid #527bbd;
|
|
}
|
|
thead {
|
|
font-family: sans-serif;
|
|
font-weight: bold;
|
|
}
|
|
tfoot {
|
|
font-weight: bold;
|
|
}
|
|
td > div.verse {
|
|
white-space: pre;
|
|
}
|
|
p.table {
|
|
margin-top: 0;
|
|
}
|
|
/* Because the table frame attribute is overriden by CSS in most browsers. */
|
|
div.tableblock > table[frame="void"] {
|
|
border-style: none;
|
|
}
|
|
div.tableblock > table[frame="hsides"] {
|
|
border-left-style: none;
|
|
border-right-style: none;
|
|
}
|
|
div.tableblock > table[frame="vsides"] {
|
|
border-top-style: none;
|
|
border-bottom-style: none;
|
|
}
|
|
|
|
|
|
div.hdlist {
|
|
margin-top: 0.8em;
|
|
margin-bottom: 0.8em;
|
|
}
|
|
div.hdlist tr {
|
|
padding-bottom: 15px;
|
|
}
|
|
dt.hdlist1.strong, td.hdlist1.strong {
|
|
font-weight: bold;
|
|
}
|
|
td.hdlist1 {
|
|
vertical-align: top;
|
|
font-style: normal;
|
|
padding-right: 0.8em;
|
|
color: navy;
|
|
}
|
|
td.hdlist2 {
|
|
vertical-align: top;
|
|
}
|
|
div.hdlist.compact tr {
|
|
margin: 0;
|
|
padding-bottom: 0;
|
|
}
|
|
|
|
.comment {
|
|
background: yellow;
|
|
}
|
|
|
|
@media print {
|
|
div#footer-badges { display: none; }
|
|
}
|
|
|
|
div#toctitle {
|
|
color: #527bbd;
|
|
font-family: sans-serif;
|
|
font-size: 1.1em;
|
|
font-weight: bold;
|
|
margin-top: 1.0em;
|
|
margin-bottom: 0.1em;
|
|
}
|
|
|
|
div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
|
|
margin-top: 0;
|
|
margin-bottom: 0;
|
|
}
|
|
div.toclevel2 {
|
|
margin-left: 2em;
|
|
font-size: 0.9em;
|
|
}
|
|
div.toclevel3 {
|
|
margin-left: 4em;
|
|
font-size: 0.9em;
|
|
}
|
|
div.toclevel4 {
|
|
margin-left: 6em;
|
|
font-size: 0.9em;
|
|
}
|
|
/* Overrides for manpage documents */
|
|
h1 {
|
|
padding-top: 0.5em;
|
|
padding-bottom: 0.5em;
|
|
border-top: 2px solid silver;
|
|
border-bottom: 2px solid silver;
|
|
}
|
|
h2 {
|
|
border-style: none;
|
|
}
|
|
div.sectionbody {
|
|
margin-left: 5%;
|
|
}
|
|
|
|
@media print {
|
|
div#toc { display: none; }
|
|
}
|
|
|
|
/* Workarounds for IE6's broken and incomplete CSS2. */
|
|
|
|
div.sidebar-content {
|
|
background: #ffffee;
|
|
border: 1px solid silver;
|
|
padding: 0.5em;
|
|
}
|
|
div.sidebar-title, div.image-title {
|
|
color: #527bbd;
|
|
font-family: sans-serif;
|
|
font-weight: bold;
|
|
margin-top: 0.0em;
|
|
margin-bottom: 0.5em;
|
|
}
|
|
|
|
div.listingblock div.content {
|
|
border: 1px solid silver;
|
|
background: #f4f4f4;
|
|
padding: 0.5em;
|
|
}
|
|
|
|
div.quoteblock-attribution {
|
|
padding-top: 0.5em;
|
|
text-align: right;
|
|
}
|
|
|
|
div.verseblock-content {
|
|
white-space: pre;
|
|
}
|
|
div.verseblock-attribution {
|
|
padding-top: 0.75em;
|
|
text-align: left;
|
|
}
|
|
|
|
div.exampleblock-content {
|
|
border-left: 2px solid silver;
|
|
padding-left: 0.5em;
|
|
}
|
|
|
|
/* IE6 sets dynamically generated links as visited. */
|
|
div#toc a:visited { color: blue; }
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<div id="header">
|
|
<h1>
|
|
cset-proc(1) Manual Page
|
|
</h1>
|
|
<h2>NAME</h2>
|
|
<div class="sectionbody">
|
|
<p>cset-proc -
|
|
manage processes running in cpusets
|
|
</p>
|
|
</div>
|
|
</div>
|
|
<h2 id="_synopsis">SYNOPSIS</h2>
|
|
<div class="sectionbody">
|
|
<div class="verseblock">
|
|
<div class="verseblock-content"><em>cset</em> [cset options] <em>proc</em> [proc options] [args]
|
|
<em>cset</em> proc --help
|
|
<em>cset</em> proc
|
|
<em>cset</em> proc my_set my_other_set
|
|
<em>cset</em> proc --list --set my_set
|
|
<em>cset</em> proc --exec my_set /opt/software/my_code --my_opt_1
|
|
<em>cset</em> proc --set my_set --exec /opt/software/my_code --my_opt_1
|
|
<em>cset</em> proc --move 2442,3000-3200 my_set
|
|
<em>cset</em> proc --move --pid=2442,3000-3200 --toset=my_set
|
|
<em>cset</em> proc --move --fromset=my_set_1 --toset=my_set_2
|
|
<em>cset</em> proc --move --pid=42 --fromset=/group1/myset --toset=/group2/yourset</div>
|
|
<div class="verseblock-attribution">
|
|
</div></div>
|
|
</div>
|
|
<h2 id="_options">OPTIONS</h2>
|
|
<div class="sectionbody">
|
|
<div class="dlist"><dl>
|
|
<dt class="hdlist1">
|
|
-h, --help
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
prints the list of options for this command
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-l, --list
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
list processes in the specified cpuset
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-e, --exec
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
execute arguments in the specified cpuset
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-u USER, --user=USER
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
use this USER to --exec (id or name)
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-g GROUP, --group=GROUP
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
use this GROUP to --exec (id or name)
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-m, --move
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
move specified tasks to specified cpuset; to move a PIDSPEC to a
|
|
cpuset, use -m PIDSPEC cpuset; to move all tasks specify --fromset
|
|
and --toset
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-p PIDSPEC, --pid=PIDSPEC
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
specify pid or tid specification
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
--threads
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
if specified, any processes found in the PIDSPEC to have multiple
|
|
threads will automatically have all their threads added to the
|
|
PIDSPEC (use to move all related threads to a cpuset)
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-s CPUSET, --set=CPUSET
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
specify name of immediate cpuset
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-t TOSET, --toset=TOSET
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
specify name of destination cpuset
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-f FROMSET, --fromset=FROMSET
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
specify name of origination cpuset
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-k, --kthread
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
move, or include moving, unbound kernel threads
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
--force
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
force all processes and threads to be moved
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-v, --verbose
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
prints more detailed output, additive
|
|
</p>
|
|
</dd>
|
|
</dl></div>
|
|
</div>
|
|
<h2 id="_description">DESCRIPTION</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>This command is used to run and manage arbitrary processes on
|
|
specified cpusets. It is also used to move pre-existing processes and
|
|
threads to specified cpusets. You may note there is no "kill" or
|
|
"destroy" option — use the standard OS ^C or kill commands for that.</p></div>
|
|
<div class="paragraph"><p>To list which tasks are running in a particular cpuset, use the --list
|
|
command.</p></div>
|
|
<div class="paragraph"><p>For example:</p></div>
|
|
<div class="paragraph"><p><strong><tt># cset proc --list --set myset</tt></strong></p></div>
|
|
<div class="paragraph"><p>This command will list all the tasks running in the cpuset called
|
|
"myset".</p></div>
|
|
<div class="paragraph"><p>Processes are created by specifying the path to the executable
|
|
and specifying the cpuset that the process is to be created in.</p></div>
|
|
<div class="paragraph"><p>For example:</p></div>
|
|
<div class="paragraph"><p><strong><tt># cset proc --set=blazing_cpuset --exec /usr/bin/fast_code</tt></strong></p></div>
|
|
<div class="paragraph"><p>This command will execute the /usr/bin/fast_code program on the
|
|
"blazing_cpuset" cpuset.</p></div>
|
|
<div class="paragraph"><p>Note that if your command takes options, then use the traditional
|
|
"--" marker to separate cset’s options from your command’s options.</p></div>
|
|
<div class="paragraph"><p>For example:</p></div>
|
|
<div class="paragraph"><p><strong><tt># cset proc --set myset --exec — ls -l</tt></strong></p></div>
|
|
<div class="paragraph"><p>This command will execute "ls -l" on the cpuset called "myset".</p></div>
|
|
<div class="paragraph"><p>The PIDSPEC argument taken for the move command is a comma
|
|
separated list of PIDs or TIDs. The list can also include
|
|
brackets of PIDs or TIDs (i.e. tasks) that are inclusive of the
|
|
endpoints.</p></div>
|
|
<div class="paragraph"><p>For example:</p></div>
|
|
<div class="literalblock">
|
|
<div class="content">
|
|
<pre><tt>1,2,5 Means processes 1, 2 and 5
|
|
1,2,600-700 Means processes 1, 2 and from 600 to 700</tt></pre>
|
|
</div></div>
|
|
<div class="admonitionblock">
|
|
<table><tr>
|
|
<td class="icon">
|
|
<div class="title">Note</div>
|
|
</td>
|
|
<td class="content">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.</td>
|
|
</tr></table>
|
|
</div>
|
|
<div class="paragraph"><p>To move a PIDSPEC to a specific cpuset, you can either specify
|
|
the PIDSPEC with --pid and the destination cpuset with --toset,
|
|
or use the short hand and list the cpuset name after the PIDSPEC
|
|
for the --move arguments.</p></div>
|
|
<div class="paragraph"><p>The move command accepts multiple common calling methods.
|
|
For example, the following commands are equivalent:</p></div>
|
|
<div class="paragraph"><p><strong><tt># cset proc --move 2442,3000-3200 reserved_set</tt></strong></p></div>
|
|
<div class="paragraph"><p><strong><tt># cset proc --move --pid=2442,3000-3200 --toset=reserved_set</tt></strong></p></div>
|
|
<div class="paragraph"><p>These commands move the tasks defined as 2442 and any running task
|
|
between 3000 and 3200 inclusive of the ends to the cpuset called
|
|
"reserved_set".</p></div>
|
|
<div class="paragraph"><p>Specifying the --fromset is not necessary since the tasks will be
|
|
moved to the destination cpuset no matter which cpuset they are
|
|
currently running on.</p></div>
|
|
<div class="admonitionblock">
|
|
<table><tr>
|
|
<td class="icon">
|
|
<div class="title">Note</div>
|
|
</td>
|
|
<td class="content">However, if you do specify a cpuset with the --fromset
|
|
option, then only those tasks that are both in the PIDSPEC <strong>and</strong>
|
|
are running in the cpuset specified by --fromset will be moved.
|
|
I.e., if there is a task running on the system but not in
|
|
--fromset that is in PIDSPEC, it will not be moved.</td>
|
|
</tr></table>
|
|
</div>
|
|
<div class="paragraph"><p>If the --threads switch is used, then the proc command will
|
|
gather any threads of belonging to any processes or threads that
|
|
are specified in the PIDSPEC and move them. This provides an easy
|
|
way to move all related threads: just pick one TID from the set
|
|
and use the --threads option.</p></div>
|
|
<div class="paragraph"><p>To move all userspace tasks from one cpuset to another, you need
|
|
to specify the source and destination cpuset by name.</p></div>
|
|
<div class="paragraph"><p>For example:</p></div>
|
|
<div class="paragraph"><p><strong><tt># cset proc --move --fromset=comp1 --toset=comp42</tt></strong></p></div>
|
|
<div class="paragraph"><p>This command specifies that all processes and threads
|
|
running on cpuset "comp1" be moved to cpuset "comp42".</p></div>
|
|
<div class="admonitionblock">
|
|
<table><tr>
|
|
<td class="icon">
|
|
<div class="title">Note</div>
|
|
</td>
|
|
<td class="content">This move command will not move kernel threads unless
|
|
the -k/--kthread switch is specified. If it is, then all unbound
|
|
kernel threads will be added to the move. Unbound kernel threads
|
|
are those that can run on any CPU. If you <strong>also specify</strong> the
|
|
--force switch, then all tasks, kernel or not, bound or not,
|
|
will be moved.</td>
|
|
</tr></table>
|
|
</div>
|
|
<div class="admonitionblock">
|
|
<table><tr>
|
|
<td class="icon">
|
|
<div class="title">Caution</div>
|
|
</td>
|
|
<td class="content">Please be cautious with the --force switch, since moving
|
|
a kernel thread that is bound to a specific CPU to a cpuset that
|
|
does not include that CPU can cause a system hang.</td>
|
|
</tr></table>
|
|
</div>
|
|
<div class="paragraph"><p>You must specify unique cpuset names for the both exec and move
|
|
commands. If a simple name passed to the --fromset, --toset and
|
|
--set parameters is unique on the system then that command
|
|
executes. However, if there are multiple cpusets by that name,
|
|
then you will need to specify which one you mean with a full path
|
|
rooted at the base cpuset tree.</p></div>
|
|
<div class="paragraph"><p>For example, suppose you have the following cpuset tree:</p></div>
|
|
<div class="literalblock">
|
|
<div class="content">
|
|
<pre><tt>/cpusets
|
|
/group1
|
|
/myset
|
|
/yourset
|
|
/group2
|
|
/myset
|
|
/yourset</tt></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>Then, to move a process from myset in group1 to yourset in
|
|
group2, you would have to issue the following command:</p></div>
|
|
<div class="paragraph"><p><tt># cset proc --move --pid=50 --fromset=/group1/myset --toset=/group2/yourset</tt></p></div>
|
|
<div class="paragraph"><p>You do not have to worry about where in the Linux filesystem the
|
|
cpuset filesystem is mounted. The cset command takes care of that.
|
|
Any cpusets that are specified by path (such as above), are done with
|
|
respect to the root of the cpuset filesystem.</p></div>
|
|
</div>
|
|
<h2 id="_license">LICENSE</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>Cpuset is licensed under the GNU GPL V2 only.</p></div>
|
|
</div>
|
|
<h2 id="_copyright">COPYRIGHT</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>Copyright (c) 2008-2011 Novell Inc.</p></div>
|
|
</div>
|
|
<h2 id="_author">AUTHOR</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>Written by Alex Tsariounov <tsariounov@gmail.com>.</p></div>
|
|
</div>
|
|
<h2 id="_see_also">SEE ALSO</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>cset(1), cset-set(1), cset-shield(1)</p></div>
|
|
<div class="paragraph"><p>/usr/share/doc/packages/cpuset/html/tutorial.html</p></div>
|
|
<div class="paragraph"><p>taskset(1), chrt(1)</p></div>
|
|
<div class="paragraph"><p>/usr/src/linux/Documentation/cpusets.txt</p></div>
|
|
</div>
|
|
<div id="footer">
|
|
<div id="footer-text">
|
|
Version 1.5.6<br />
|
|
Last updated 2011-06-09 12:52:44 EDT
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|