"David S. Miller" wrote: > 2) It affects only code which can burn a lot of cpu without > scheduling. Compare this to schemes which make the kernel > fully pre-emptable, causing _EVERYONE_ to pay the price of > low-latency.... Is there necessarily a price? Kernel preemption can make io-bound code go faster by allowing a blocked task to start running again immediately on io completion. As things are now, the task will have to wait for whatever might be happening in the kernel to complete. -- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- low-latency scheduling patch for 2.4.0 Andrew Morton
- Re: [linux-audio-dev] low-latency scheduling patch fo... Jay Ts
- Re: [linux-audio-dev] low-latency scheduling patc... Cort Dougan
- Re: [linux-audio-dev] low-latency scheduling patc... Andrew Morton
- Re: [linux-audio-dev] low-latency scheduling ... David S. Miller
- Re: [linux-audio-dev] low-latency schedul... Daniel Phillips
- Re: [linux-audio-dev] low-latency schedul... Nigel Gamble
- Re: [linux-audio-dev] low-latency sc... David S. Miller
- Re: [linux-audio-dev] low-latenc... george anzinger
- Re: [linux-audio-dev] low-latency sc... Andrew Morton
- Re: [linux-audio-dev] low-latenc... Tim Wright
- Re: [linux-audio-dev] low-la... Nigel Gamble
- Re: [linux-audio-dev] low-la... Andrew Morton
- Re: [linux-audio-dev] low-la... Tim Wright
- Re: [linux-audio-dev] low-latenc... Nigel Gamble
- Re: [linux-audio-dev] low-latenc... george anzinger