On Mon, 2005-05-30 at 19:32 -0400, James Bruce wrote:
> This is sort of confused
> by the fact that Ingo called it "hard realtime" because he measured a
> maximum latency during a stress test. Unfortunately that's not
> really
> hard realtime if you are just measuring it; Rather its "really damn
> good
> soft realtime". An analysis of code paths could be done to determine
> if
> something really does satisfy hard-RT constraints, but to my
> knowledge
> that's not on the table at this point. So you're discussing soft
> realtime if you're dicussing the RT patch.
>
> So its really just a misunderstanding
No, *you're* the one misunderstanding.
Since *everything* is preemptible except a few known code paths whose
execution times determine the maximum possible latency from interrupt to
running the highest priority user process.
That's the determinism, no more, no less. But some people inexplicably
think this thread is about providing deterministic hard RT performance
for some subset of system calls, or disk IO or something, none of which
have anything to do with PREEMPT_RT.
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
