Messages in this thread | | | Date | Wed, 27 Jun 2001 15:40:36 -0700 | From | Mike Kravetz <> | Subject | Re: wake_up vs. wake_up_sync |
| |
On Wed, Jun 27, 2001 at 02:57:43PM -0700, Scott Long wrote: > Does reschedule_idle() ever cause the current CPU to get scheduled? That > is, if someone calls wake_up() and wakes up a higher-priority process > could reschedule_idle() potentially immediately switch the current CPU > to that higher-priority process?
No. reschedule_idle() never directly performs a 'task to task' context switch itself. Instead, it simply marks a currently running task to indicate that a reschedule is needed on that task's CPU. No task context switch will occur until schedule() is run on that CPU.
-- Mike Kravetz mkravetz@sequent.com IBM Linux Technology Center - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |