On Monday 14 January 2002 13:17, Momchil Velikov wrote: > >>>>> "yodaiken" == yodaiken <yodaiken _at_ fsmlabs.com> writes: > > yodaiken> It's not even clear how preempt is supposed to interact with > SCHED_FIFO. > > How so ? The POSIX specification is not clear enough or it is not to be > followed ? You can have an rt task block on a lock held by a normal task that was preempted by a rt task of lower priority. The same problem as with the sched_idle patches. Regards Oliver - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [2.4.17/18pre] VM and swap - it's really unusableMomchil Velikov <velco _at_ fadata.bg>
- Re: [2.4.17/18pre] VM and swap - it's really unusableAlan Cox <alan _at_ lxorguk.ukuu.org.uk>
- Re: [2.4.17/18pre] VM and swap - it's really unusableyodaiken _at_ fsmlabs.com
- Re: [2.4.17/18pre] VM and swap - it's really unusableMomchil Velikov <velco _at_ fadata.bg>
- Prev by Date: tmpfs accounting (was: losetuping files in tmpfs fails?)
- Next by Date: Re: PROBLEM: System locks up after "spurious 8259A interrupt: IRQ7"
- Previous by thread: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Next by thread: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Indexes:[Main][Thread]