On 2018-07-30 15:00:00 [+0200], Daniel Bristot de Oliveira wrote: > Before calling __schedule() to cause a context switch, the schedule() > function runs sched_submit_work() to dispatch deferred work that was > postponed to the point that the thread is leaving the processor. > The function sched_submit_work() checks for the need to wake up a > kworker; if needed, a kworker thread is awakened. In this context, > the following behavior takes place. … > at line 11, there is nothing to schedule, and so the __schedule() at > line 18 is called in vain. I read this as an optimisation for the common case as you put it. Applied. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
