9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Michael Teichgräber" <mt@wmipf.in-berlin.de>
To: 9fans@cse.psu.edu
Subject: [9fans] devrealtime
Date: Fri,  6 Jul 2007 02:21:05 +0200	[thread overview]
Message-ID: <468D8AF1.2090400@wmipf.in-berlin.de> (raw)

Hi,

I have just tried the realtime scheduler using `echo's of period, cost,
admit into the /proc/.../ctl of a test program.

In a 9fans posting I have seen another example where a real-time process
was created by opening /dev/realtime/clone. This usage pattern looks
interesting; a task that needs real-time conditions is not a real-time
task itself, but uses such a task to get the desired timing (this is at
least my understanding of it).

Apparently devrealtime.c has been removed from the kernel some time ago.
Likely this interface is obsolete, and the devproc one is current.

How would I use that properly? I suppose a task could write to its own
/proc/.../ctl to enable real-time mode. Is there an example available
similar to the devrealtime one?

Thanks,
Michael


                 reply	other threads:[~2007-07-06  0:21 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=468D8AF1.2090400@wmipf.in-berlin.de \
    --to=mt@wmipf.in-berlin.de \
    --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).