From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: J Sloan <joe@tmsusa.com>, linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Adeos nanokernel for Linux kernel
Date: Wed, 05 Jun 2002 13:15:26 +0200 [thread overview]
Message-ID: <3CFDF2CE.3070307@loewe-komp.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0206041418460.2614-100000@waste.org> <E17FQPj-0001Rr-00@starship> <3CFD8C07.6030607@tmsusa.com> <E17FS6T-0001UR-00@starship>
Daniel Phillips wrote:
> On Wednesday 05 June 2002 05:56, J Sloan wrote:
>
>>Daniel Phillips wrote:
>>
>>
>>>If I recall correctly, XFS makes an attempt to provide such realtime
>>>guarantees, or at least the Solaris version does.
>>>
>>>
>>When did Solaris ever support xfs?
>>
>>
>>>However, the operating
>>>system must be able to provide true realtime guarantees in order for the
>>>filesystem to provide them, and I doubt that the combination of XFS and
>>>Solaris can do that.
>>>
>>>
>>no, but the combination of xfs and irix has
>>
> ^^^^
> Heh, I can only protest that Oxymoron also missed that thinko..
>
>
>>made a lot of folks happy - and xfs/linux is coming along nicely as
>>well...
>>
>
> Improving the average latency of systems is a worthy goal, and there's
> no denying that 'sorta realtime' has its place, however it's no substitute
> for the real thing. A soft realtime system screws up only on occasion,
> but - bugs excepted - a hard realtime system *never* does.
>
Yes, in theory. You define hard realtime system in a clean room.
Even QNX4 couldn't provide hard realtime when creating new processes.
You had to start them beforehand - so you needed good system design.
The OS is just a small part of that.
Even vxworks had problems with priority inversion ... and so on.
next prev parent reply other threads:[~2002-06-05 11:13 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 8:35 [ANNOUNCE] Adeos nanokernel for Linux kernel Karim Yaghmour
2002-06-03 8:46 ` Erik Andersen
2002-06-03 8:56 ` Alessandro Rubini
2002-06-03 9:14 ` Karim Yaghmour
2002-06-03 9:52 ` Erik Andersen
2002-06-03 10:05 ` Alessandro Rubini
2002-06-03 10:12 ` Karim Yaghmour
2002-06-03 10:33 ` Erik Andersen
2002-06-03 10:38 ` Karim Yaghmour
2002-06-03 11:05 ` Daniel Phillips
2002-06-03 9:26 ` Daniel Phillips
2002-06-04 19:29 ` Oliver Xymoron
2002-06-05 2:20 ` Daniel Phillips
2002-06-05 2:40 ` Oliver Xymoron
2002-06-05 2:57 ` Daniel Phillips
2002-06-05 13:51 ` Oliver Xymoron
2002-06-05 14:25 ` Daniel Phillips
2002-06-05 15:37 ` Oliver Xymoron
2002-06-05 17:32 ` Daniel Phillips
2002-06-05 18:06 ` Mark Mielke
2002-06-05 18:26 ` Daniel Phillips
2002-06-05 19:13 ` Oliver Xymoron
2002-06-05 19:40 ` Daniel Phillips
2002-06-05 20:51 ` Mark Mielke
2002-06-05 21:45 ` Daniel Phillips
2002-06-05 21:22 ` Oliver Xymoron
2002-06-05 21:55 ` Daniel Phillips
2002-06-06 8:52 ` Peter Wächtler
2002-06-06 10:58 ` Daniel Phillips
2002-06-06 14:03 ` Peter Wächtler
2002-06-06 16:53 ` Daniel Phillips
2002-06-05 20:48 ` Mark Mielke
2002-06-06 8:34 ` Peter Wächtler
2002-06-08 13:50 ` john slee
2002-06-08 13:59 ` Thunder from the hill
2002-06-06 21:21 ` Pavel Machek
2002-06-07 1:35 ` Mark Mielke
2002-06-07 2:42 ` Daniel Phillips
2002-06-07 2:48 ` Mark Mielke
2002-06-07 10:32 ` Daniel Phillips
2002-06-07 21:35 ` Pavel Machek
2002-06-05 9:41 ` Ingo Oeser
2002-06-05 18:20 ` Karim Yaghmour
2002-06-05 3:56 ` J Sloan
2002-06-05 4:08 ` Daniel Phillips
2002-06-05 7:28 ` Eric W. Biederman
2002-06-05 11:15 ` Peter Wächtler [this message]
2002-06-05 12:56 ` Daniel Phillips
2002-06-05 11:11 ` Peter Wächtler
2002-06-05 16:55 ` Rob Landley
2002-06-04 16:10 ` Pavel Machek
2002-06-04 19:59 ` Karim Yaghmour
2002-06-04 21:53 ` Karim Yaghmour
2002-06-04 23:06 ` Alan Cox
2002-06-05 4:00 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 9:24 Martin.Knoblauch
2002-06-05 19:01 Paul Zimmerman
2002-06-05 19:11 ` Karim Yaghmour
2002-06-05 20:17 ` Daniel Phillips
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=3CFDF2CE.3070307@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.