Originally Posted by trist007
By enabling this kernel option does this make my machine a realtime machine?
What does this really mean?
In theory, when a process runs that process runs in realtime meaning it has full control of the system. So theoretically, the process would release control once the process end.
However, what would happen if that process running in realtime crashes? Then it would never release the command to stop and hand the CPU over to another process ending up in a total freeze up
Is this understanding correct?
What are some applications of realtime kernel? Midi sequencing? Audio synching?
No, you have misunderstood, probably both real time and tickless
. Essentially, tickless is (strictly, enables) a lower power idle state, although this
old testing doesn't show much difference. And this is unconnected with real time.
RH document seems to show them unconcerned about whether it is advantageous or not.)
On the other hand, real time is all about deadlines; can you guarantee that a certain thing will occur by some specified deadline and how important is it, if that does not occur (do people die. which should really be avoided at all costs or is it just a bit undesirable, so it is worth taking measures to minimise, but if it happens infrequently, it might not be a big problem?).
Sometimes people think that realtime is equivalent to fast, and that is a mistake.
Realtime is often relevant to embedded control applications and (oddly) to enterprise database applications in which deadlines for (and coherency of) transfer of numbers with lots of zeros at the end is relevant. And, music, as you mentioned...although choppy music reproduction doesn't kill all that many, on an annualised basis.