Hi,

Why is Linux kernel considered a (hard) realtime OS? I already
understand the basic reason is that the linux kernel does not
guarantee that a task will be completed on time. But I would
appreciate answers in terms of more of kernel jargons.

What stops us from classifying kernel as hard RTOS? Is it because at
times the kernel is non-preemptive (for e.g. while holding spinlocks)?
Has it got something to do with interrupt latency / scheduling latency
etc?

Is the behaviour of the kernel (when it is preemptive) similar to hard
real time OS ??

Thanks,

Rick
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to