From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] commercial deployment
Date: Fri, 20 Jul 2001 17:52:59 -0400 [thread overview]
Message-ID: <200107202152.RAA04992@smarty.smart.net> (raw)
In-Reply-To: <ycdae1zmu03.fsf@tiger.cs.yorku.ca> from "Ozan Yigit" at Jul 20, 2001 04:47:32 PM
>
> well, to be fair, there exists a number of "real-time" extensions to linux
> with variable levels of usefullness. i looked at about four of them [one
> of them with a patent and a ton of apologists :/] and i figure none of them
> will make it to OS proper (bazaar? ahahahaha). also none of them, so far as
> i can see would satisfy "hard" real time needs which was the reason for my
> looksee. (eg. pre-run-time scheduling with constraints) so i can see why it
What are "pre-run-time scheduling with constraints" and how does rtlinux
fail there? It sounds like it's pretty hard realtime to me. I was looking
at the IRQ stuff in Linux 1.2.13 though, and I don't see why there just
isn't a _RT_<num>interrupt .
Rick Hohensee
www.clienux.com
next prev parent reply other threads:[~2001-07-20 21:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 19:28 anothy
2001-07-19 20:36 ` Mike Haertel
2001-07-19 22:34 ` Fariborz 'Skip' Tavakkolian
2001-07-20 8:59 ` Alberto Nava
2001-07-20 16:47 ` Ozan Yigit
2001-07-20 21:52 ` Rick Hohensee [this message]
2001-07-24 11:34 ` Ozan Yigit
2001-07-25 1:40 ` Rick Hohensee
2001-07-25 3:52 ` Boyd Roberts
2001-07-25 8:10 ` [9fans] more lucent bad news - another 15,000 to 20,000 jobs to go Matt
2001-07-26 8:48 ` [9fans] commercial deployment Ozan Yigit
2001-07-20 21:56 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-07-26 11:55 rob pike
2001-07-26 13:23 ` Boyd Roberts
2001-07-26 14:01 ` Rick Hohensee
2001-07-26 15:38 ` Ozan Yigit
2001-07-21 17:32 bwc
2001-07-20 14:20 bwc
2001-07-21 9:53 ` Steve Kilbane
2001-07-19 8:24 Stephen King
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=200107202152.RAA04992@smarty.smart.net \
--to=humbubba@smarty.smart.net \
--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).