> This is precisely the sort of design limitation we're tearing down with
> these hybrid realtime/non-realtime systems. Your mistake is assuming
> that every form of communication between the two has to be tightly
No, the mistake is assuming that loosely coupling UNIX to RT lets you
leverage much of anything from UNIX. The whole attraction of a hybrid
system is the idea of building an app in a "normal" operating system on
top of a realtime layer because it's much easier to code for normal
operating system than realtime. Normal operating systems lets you have
real stacks and memory management and paging and fast filesystems and TCP
and load >= 1.
And your MP3-player example is a great one of where you don't get much out
of it. You have to rewrite _everything_ to run in the RT space. Yes,
doable, but how is it better from a developer perspective than the
duct-taped RIO approach? Tape it inside the box with USB (there's your
shared filesystem) if that makes you happier.
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/