From: "Mark F Rodriguez" <macrod@xaplos.com>
To: "'Fans of the OS Plan 9 from Bell Labs'" <9fans@cse.psu.edu>
Subject: RE: [9fans] A prick into the wasps' nest ;-)
Date: Tue, 8 Jun 2004 15:39:54 -0400 [thread overview]
Message-ID: <20040608194001.ESJB13581.imf17aec.mail.bellsouth.net@Xaplos> (raw)
In-Reply-To: <12e84147b06e768c84bc4058436b7a6b@vitanuova.com>
> inferno does not currently have any realtime support. (it's not
> clear to what extent this could be done on a non-native
> platform anyway).
I'm not sure about other platforms, but don't Linux(2.6), FreeBSD Plan9
(from reading man proc), and Windows support [soft] realtime within the OS
out-of-the-box? I know you can get a POSIX 1003.1b implementation to bring
your OS (at least those with source available) up to realtime specs. Perhaps
one could [re]build the platform emu with a flag setting specifying whether
or not they have realtime support (Windows, Plan9 or POSIX)???
I can easily see how this could present a challenge on non-native platforms
even if the hosting platform had real-time support, but I can also see great
benefits to having realtime capabilities within native Inferno. Are there no
plans to support proc (perhaps with different results depending on host w/o
realtime support vs. native Inferno or host with realtime support)?
>
> also, its process device is called "prog", not "proc", so "man prog"
> or "wm/man prog" gives a more useful result.
Thanks for the clarification, I had recently read man prog but was hoping
the realtime features of proc (i.e., period, deadline, cost, yieldonblock,
etc.) where somewhere hidden within Inferno.
Thanks,
-Mark
next prev parent reply other threads:[~2004-06-08 19:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 7:09 cej
2004-06-07 15:53 ` Rob Pike
2004-06-08 7:32 ` Vladimir Los
2004-06-08 11:00 ` [9fans] wasp's answer... :o) Vladimir Los
2004-06-08 18:18 ` [9fans] A prick into the wasps' nest ;-) Sape Mullender
2004-06-08 18:55 ` Mark F Rodriguez
2004-06-08 18:58 ` William Josephson
2004-06-08 19:05 ` rog
2004-06-08 19:39 ` Mark F Rodriguez [this message]
2004-06-08 20:50 ` boyd, rounin
[not found] ` <40C6C6E8.1000302@chunder.com>
2004-06-20 22:35 ` vdharani
2004-06-08 6:51 cej
2004-06-08 8:17 ` Vladimir Los
2004-06-09 23:10 ` kim kubik
2004-06-09 23:22 ` boyd, rounin
2004-06-09 23:40 ` George Michaelson
2004-06-09 23:41 ` boyd, rounin
2004-06-09 23:41 ` andrey mirtchovski
2004-06-09 23:44 ` boyd, rounin
2004-06-09 23:55 ` Geoff Collyer
2004-06-09 23:27 ` rog
2004-06-10 8:03 ` Vladimir Los
[not found] <40C6C916.5080004@chunder.com>
2004-06-09 15:04 ` Mark F Rodriguez
2004-06-09 16:04 ` Bruce Ellis
2004-06-09 16:08 ` rog
2004-06-09 16:11 ` Bruce Ellis
2004-06-09 18:54 ` boyd, rounin
[not found] <20040609125113.UCQG24541.imf23aec.mail.bellsouth.net@Xaplos>
[not found] ` <4fa4328626f76766f4799367fc0550c7@vitanuova.com>
2004-06-09 18:41 ` boyd, rounin
2004-06-10 8:16 ` vdharani
2004-06-10 3:25 ` boyd, rounin
2004-06-10 5:45 ` Nigel Roles
2004-06-10 9:20 ` Steve Simon
2004-06-10 9:20 ` Bruce Ellis
2004-06-10 14:55 ` boyd, rounin
2004-06-10 9:43 Andrew Simmons
2004-06-10 10:36 ` Nigel Roles
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=20040608194001.ESJB13581.imf17aec.mail.bellsouth.net@Xaplos \
--to=macrod@xaplos.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).