From: Uriel <uriel99@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: [sources] 20070413: /rc/bin/cpurc.local
Date: Sun, 15 Apr 2007 10:06:13 +0200 [thread overview]
Message-ID: <5d375e920704150106m5865747flb6ae25392f8744ca@mail.gmail.com> (raw)
In-Reply-To: <f93786a38200d44b7406b3181b4e2c20@cat-v.org>
On Sat, 14 Apr 2007 06:17:24, 9changes@cat-v.org <9changes@cat-v.org> wrote:
> + # turn on cooperative scheduling (assuming it starts off)
> + echo coop > /dev/reboot
> [geoff] --rwxrwxr-x M 121 geoff sys 448 Apr 13 18:06 rc/bin/cpurc.local
What does this do? It is undocumented, and as far as I can tell it
toggles the coopsched var, which is used once in the scheduler code.
Would be nice to know what it does exactly, and why on earth it uses
/dev/reboot. Note that there is no way to check the state of the
variable, so one has no clue if one is enabling or disabling
'coopsched', whatever it does this interface is clearly far from
ideal.
While investigating this I noticed a couple of other undocumented
commands for /dev/reboot that seem more relevant and self-evident but
would still be nice to have documented.
Best wishes
uriel
next parent reply other threads:[~2007-04-15 8:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f93786a38200d44b7406b3181b4e2c20@cat-v.org>
2007-04-15 8:06 ` Uriel [this message]
2007-04-15 17:00 ` Uriel
2007-04-15 17:26 ` Devon H. O'Dell
2007-04-15 17:35 ` erik quanstrom
2007-04-15 17:37 ` Devon H. O'Dell
2007-04-15 17:38 ` Russ Cox
2007-04-15 17:43 ` Uriel
2007-04-15 20:31 ` Devon H. O'Dell
2007-04-15 17:43 ` Devon H. O'Dell
2007-04-15 17:59 ` Russ Cox
2007-04-15 20:34 ` Devon H. O'Dell
2007-04-17 5:21 ` Russ Cox
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=5d375e920704150106m5865747flb6ae25392f8744ca@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).