From: Jason Baietto <jason.baietto@ccur.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Multiprocessor Control Interfaces (update)
Date: 13 Dec 2001 16:56:21 -0500 [thread overview]
Message-ID: <1008280587.5764.4.camel@tofu> (raw)
A new version of my proposed multiprocessor control interfaces
is available here:
http://www.ccur.com/realtime/oss
This version has some fixes and documentation updates and
incorporates some of the recent suggestions that I've received.
Here's the latest help output from run:
Usage: run [OPTIONS] { COMMAND [ARGS] | PROCESS_SPECIFIER }
Set scheduling parameters and CPU bias for a new process or a list
of existing processes.
OPTIONS can be one or more of the following options:
-b, --bias=LIST Set the CPU bias to the LIST of CPUs;
CPUs are numbered starting from 0
-s, --policy=POLICY Set the scheduling policy to POLICY
-P, --priority=LEVEL Set the scheduling priority to LEVEL
-q, --quantum=QUANTUM Set the SCHED_RR quantum to QUANTUM
-N, --negate Negate the CPU bias list; all CPUs
except those listed will be selected
-f, --fork Fork COMMAND and return immediately
-V, --version Output version information and exit
-v, --verbose Output information before each action
-h, --help Display this help and exit
PROCESS_SPECIFIER is exactly one of the following options:
-p, --pid=LIST Specify LIST of existing PIDs to modify
-g, --group=LIST Specify LIST of process groups to modify; all
existing processes in the groups will be modified
-u, --user=LIST Specify LIST of users to modify; all existing
processes owned by the users will be modified
-n, --name=LIST Specify LIST of existing process names to modify
Multiple comma separated values can be specified for all LISTs and ranges
are allowed where appropriate (e.g. "run -b 0,2-5 autopilot").
See the run(1) man page for more information.
Take care,
Jason
--
Jason Baietto
jason.baietto@ccur.com
reply other threads:[~2001-12-13 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1008280587.5764.4.camel@tofu \
--to=jason.baietto@ccur.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.