> P.S. IMVHO the xine problem is completely different as has nothing to
> with interactivity but with the fact that it is soft
> real-time. i.e. you need to distingish xine from say a gimp filter or
> a 3D renderer with incremental live updates of the scene it is
> creating.
Xine is the same as X or vi or xmms, for this problem.
They are all, in fact, soft real-time issues where the latency limit we
want is whatever is the threshold of human perception. This limit may
be more or less for DVD playback vs. typing vs. music playback... but
ultimately there is some latency threshold you want maintained. If Xine
is starved too long, your video skips. If vi is starved too long, you
can perceive a lag in your keystrokes showing up. It is all the same.
Maybe we do not care about the latency of the gimp filter. Those are
indeed different. But the interactivity of other things - say, gimp's
menus in response to you clicking them - are all the same sort of thing.
Robert Love
-
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/