Ingo Molnar <[EMAIL PROTECTED]> writes: > * Nick Piggin <[EMAIL PROTECTED]> wrote: > >> But the important elements are lost. The standard provides a >> deterministic scheduling order, and a deterministic scheduling latency >> (of course this doesn't mean a great deal for Linux, but I think we're >> good enough for a lot of soft-rt applications now). >> >> > [1] http://www.opengroup.org/onlinepubs/007908799/xsh/realtime.html > > no, the patch does not break POSIX. POSIX compliance means that there is > an environment that meets POSIX. Any default install of Linux 'breaks' > POSIX in a dozen ways, you have to take a number of steps to get a > strict, pristine POSIX environment. The only thing that changes is that > now you have to add "set RT_CPU ulimit to 0 or 100" to that (long) list > of things.
I agree. Is the rest of this list documented somewhere? -- joq - 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/
