9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] /dev/realtime doesn't exist?
Date: Tue, 29 Aug 2023 12:45:35 -0700	[thread overview]
Message-ID: <CAJSxfmKGnjuM-0fAeVTLVJwGWypj98Bpsca4kRPowXz5guX+aw@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5j6=DdNLcJneoA4GmmtvSTUOzRJHHzPub07Z0gOWFBXKg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

I wrote an example 20 years ago, but couldn't get it to work. I found a
copy in this thread:


On Tue, Aug 29, 2023, 11:29 AM Charles Forsyth <charles.forsyth@gmail.com>

> 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, <ori@eigenstate.org> wrote:
>> Quoth dusan3sic@gmail.com:
>> > I was reading an article about plan9's realtime scheduler edf (
>> http://doc.cat-v.org/plan_9/real_time/real_time_in_a_real_operating_system/real_time_in_a_real_operating_system.pdf,
>> 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 days?
>> 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
>> survive?)
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Td0e7a4f73d1eae3b-M6b463332615f9ce69ce32d0b>

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td0e7a4f73d1eae3b-Ma9390b0283a268af33ad6e82
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 3950 bytes --]

      reply	other threads:[~2023-08-29 19:46 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
2023-08-29 19:45     ` Skip Tavakkolian [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJSxfmKGnjuM-0fAeVTLVJwGWypj98Bpsca4kRPowXz5guX+aw@mail.gmail.com \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \


* 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).