On 28-Aug-2000 Linus Torvalds wrote:
> I think the right solution is to completely split up "schedule()" into two
> different functions (which just share 99% of the code), and basically have
> the idle thread call the _other_ schedule. The one that never does the
> test at all.
Just to clarify, you're suggesting having a schedule_and_btw_current_is_idle
and calling this from cpu_idle(), right? In this case the two schedules
would share quite a bit less than 99% of the code. Idle tasks don't have to
deal with kernel lock, ->state, SCHED_YIELD and RT exhaustion, to name a few.
Instead, they might deal with more productive things such as direct handoff
of a process that just went through reschedule_idle and selected an idle cpu.
-- Dimitris Michailidis dimitris@engr.sgi.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:22 EST