Good point. Quake deathmatch is another place where you worry a lot
about your controls being realtime.
> > But it's not too hard to do. Just allow the RTOS to take control of the
> > input devices, or at least to insert itself ahead of the general purpose
> > operating system in the interrupt pipeline.
> >
> > As for a GUI with realtime response characteristics, that's more
> > challenging, but it has been done. It's also less important I'd say. You
> > can always fall back on dedicated hardware for the realtime display.
>
> Of course, but then it's no longer part of a general-purpose operating
> system. Baby, bathwater. It's easier to tape a Rio onto the side of your
> machine.
Not at all. You can still run a web browser and a download in parallel
with the realtime process, that's the beauty of it. As for the realtime
gui, if you're determined to build one it doesn't have to be the whole
desktop. It can just be one window, much like a video overlay.
I'm don't see any fundamental roadblock here.
> > > What you really want for an MP3 player is _not_ hard RT, what you want is
> > > very reliable low-latency. Which we can do without throwing away most of
> > > UNIX.
> >
> > I think that depends on whether you are an audiophile or not. Or a
> > broadcaster. If you're a broadcaster, how many mp3 skips will you tolerate
> > a year?
>
> If the number is zero, you can't use the facilities of a non-RT operating
> system for anything except (possibly lossily) monitoring the output of
> such a system.
That doesn't follow. I ought to be able to do an apt-get dist-upgrade
without the realtime application ever skipping a beat, just to pick one
example off the top of the pile.
> If you feed an RT system with data or control from a non-RT
> system, it becomes a non-RT system. If you try to losslessly queue output
> from an RT system to a non-RT system, it becomes a non-RT system.
If it hurts, don't do that. I thought we'd invoked the concept of a
realtime filesystem? You can log to that, and you ought to be able to
run queries against it in non-realtime. You don't have to suck the
entire world into your realtime application.
> > And who said anything about throwing away most of Unix?
>
> You did, by insisting on absolutes. Hard realtime places many restrictions
> on what you can do - it's like having your entire system inside an
> interrupt context or a signal handler.
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
coupled. It's true that the entire realtime system has to operate
within the strictures of some formalism, but that's what formalisms
are for. It's no more shocking a limitation than the fact that regular
users aren't allowed to do all the things the superuser can do.
-- Daniel - 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/