9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] /dev/realtime doesn't exist?
Date: Tue, 29 Aug 2023 13:18:09 -0400	[thread overview]
Message-ID: <15AECCB2DF4CE07D4E8FD30E13EF1598@eigenstate.org> (raw)
In-Reply-To: <16933060120.86e7cFDc.27169@composer.9fans.topicbox.com>

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

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

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

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=15AECCB2DF4CE07D4E8FD30E13EF1598@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).