On Tue, 2002-01-08 at 19:29, John Alvord wrote: > The best part about planned preemption points is that there is minimal > state to save when an interruption occurs. Actually, both preempt-kernel and low-latency do about the same amount of work re saving state. With preempt-kernel, when a task is preempted in-kernel we AND a flag value into the preempt count. That is all we need to keep track of things. With low-latency, the task state is set to TASK_RUNNING (which is a precautionary measure). So it is about the same, although low-latency (and lock-break) often also have to do various setup with the locks and all. Robert Love - 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/
References:
- Re: [2.4.17/18pre] VM and swap - it's really unusableKen Brownfield <brownfld _at_ irridia.com>
- 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 unusableJohn Alvord <jalvo _at_ mbay.net>
- Prev by Date: Re: Problem with network
- Next by Date: Re: [PATCH] C undefined behavior fix
- 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]