From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: rlrevell@joe-job.com
Subject: Re: [patch] IRQ threads
Date: 29 Jul 2004 16:33:20 -0400 [thread overview]
Message-ID: <1091133199.1232.1384.camel@cube> (raw)
Lee Revell writes:
> As I understand it there will still be a place for the
> current hard-RT Linux solutions, because even if I can
> get five nines latency better than N, this is not good
> enough for hard RT, as you need to be able to mathematically
> demonstrate that you can *never* miss a deadline.
Nah, that's academic theory. There is no such thing
as hard-RT in the real world.
In reality, there's no point in making the software far
more reliable than the hardware, power supply, and so on.
Somebody may pour a can of Mountain Dew into the vent holes.
Your software is OK as long as other causes of failure
are much more likely. One might even say you spent too
much of your budget perfecting the software! In the end it
all comes down to $$$ (or Euros, or Yen...), doesn't it?
People don't mathematically demonstrate anything about
modern systems, at least not while being honest. Modern
systems have cache memory, interrupts. compiled code...
Use an Intel 4004 if you want mathematical proofs, and
even then, remember the can of Mountain Dew. (and bugs!)
Heh, your proof could be buggy. Then what?
Math problem:
The cost of the system is inversly proportional to the
likelyhood of failure. Set the likelyhood of failure
to zero and solve for the cost. :-)
That won't make the customer happy.
next reply other threads:[~2004-07-29 23:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 20:33 Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 22:50 [patch] IRQ threads Scott Wood
2004-07-28 6:27 ` Ingo Molnar
2004-07-28 15:38 ` Karim Yaghmour
2004-07-28 16:01 ` Karim Yaghmour
2004-07-28 21:23 ` Bill Huey
2004-07-28 21:35 ` Scott Wood
2004-07-29 21:08 ` Bill Huey
2004-07-29 22:44 ` Ingo Molnar
2004-07-28 23:24 ` Scott Wood
2004-07-28 8:10 ` Ingo Molnar
2004-07-28 23:12 ` Scott Wood
2004-07-29 19:33 ` Ingo Molnar
2004-07-29 20:21 ` Scott Wood
2004-07-29 21:12 ` Alan Cox
2004-07-28 15:45 ` Karim Yaghmour
2004-07-28 18:28 ` Lee Revell
2004-07-28 19:12 ` Karim Yaghmour
2004-07-28 19:33 ` Lee Revell
2004-07-28 19:57 ` Karim Yaghmour
2004-07-28 20:35 ` Lee Revell
2004-07-28 21:15 ` Karim Yaghmour
2004-07-28 21:43 ` Lee Revell
2004-07-28 21:38 ` Karim Yaghmour
2004-07-28 20:21 ` Bill Huey
2004-07-28 20:42 ` Lee Revell
2004-07-28 20:46 ` Bill Huey
2004-07-28 21:48 ` Karim Yaghmour
2004-07-28 22:30 ` Bill Huey
2004-07-28 22:03 ` Philippe Gerum
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=1091133199.1232.1384.camel@cube \
--to=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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