Page 1 of 1

Interrupt on/off control

PostPosted: Fri Oct 05, 2012 5:49 pm
by dbwalker
What was the reasoning behind disabling interrupts when searching for the next task to run? I understand that you may want to change the state of a task in an ISR, but by disabling interrupts, you always defer it until the end. It would seem to me that leaving the interrupts disabled would possibly cause a task to be marked running a little bit sooner, but wouldn't cause any other bad side effects.

Thanks,
David Walker

Re: Interrupt on/off control

PostPosted: Sun Oct 07, 2012 5:54 pm
by peter
Yes, you are right. There are no good reason to disable interrupts there. I will remove it.
/Peter