On Sun, 2019-08-18 at 17:49 -0400, Joel Fernandes (Google) wrote: > When we're in hard interrupt context in rcu_read_unlock_special(), we > can still benefit from invoke_rcu_core() doing wake ups of rcuc > threads when the !use_softirq parameter is passed. This is safe > to do so because: What is the benefit, beyond skipping the irq work overhead? Is there some reason to specifically want the rcuc thread woken rather than just getting into the scheduler (and thus rcu_note_context_switch) as soon as possible? -Scott
