From: Charles Forsyth <email@example.com>
To: 9fans <firstname.lastname@example.org>
Subject: Re: [9fans] /dev/realtime doesn't exist?
Date: Tue, 29 Aug 2023 19:27:09 +0100 [thread overview]
Message-ID: <CAOw7k5j6=DdNLcJneoA4GmmtvSTUOzRJHHzPub07Z0gOWFBXKg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
There's another paper from an iwp9 http://9p.io/iwp9/Real-time.pdf that
might provide more detail
On Tue, 29 Aug 2023 at 18:19, <email@example.com> wrote:
> Quoth firstname.lastname@example.org:
> > I was reading an article about plan9's realtime scheduler edf (
> page 7), and they mentioned using /dev/realtime to create realtime
> processes, but /dev/realtime doesn't exist on my machine (I am using
> 9front). I found a post here from 07 saying something about removing it a
> long time ago, but it got no answers.
> > In proc(3) they mention some commands for configuring realtime processes
> but I don't know if that is to configure an already made realtime process
> or to make one from a regular. How do i make realtime processes in these
> it's the bits you found in /proc; there are no (longer?)
> any special real time processes; any process can become
> real time by setting up deadlines at any point.
> /dev/realtime isn't needed any more.
> unfortunately, I'm not aware of any programs using it.
> (that may be a good question for the list: where was the
> real time scheduler used, and does any code using it
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3075 bytes --]
next prev parent reply other threads:[~2023-08-29 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 10:46 dusan3sic
2023-08-29 17:18 ` ori
2023-08-29 18:27 ` Charles Forsyth [this message]
2023-08-29 19:45 ` Skip Tavakkolian
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).