Re: Attempted summary of "RT patch acceptance" thread

[Andrea Arcangeli <andrea@suse.de>]

On Fri, Jun 10, 2005 at 03:37:24PM -0700, Bill Huey wrote:
> Some of the comments from various folks are just intolerably paranoid

Just tell me how can you go to a customer and tell him that your
linux-RTOS has a guaranteed worst case latency of 50usec.  How can you
tell that? Did you exercise all possible scheduler paths with cache
disabled and calculated the worst case latency with rdtsc + math?

Why do you take risks when you can go with much more relaible solutions
like RTAI and rtlinux?

Using metal-hard RTOS in things that requires ruby-hard deadline
guarantee, seems just an unnecessary risk. I'd prefer you to be
more paranoid and less relaxed about these issues, there are enough bugs
and risks even when one does the best and is very paranoid.

Said that there are many problems where metal-hard solutions are
fine, every single app that don't require a worst-case guarantee of
the worst-case latency is fine with metal-hard, and every time one has
to call into the alsa ioctl or other complex syscalls also is fine with
metal hard since the first kmalloc or lock contention inside RT context,
will send your RTOS into water-hard state.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/