On Tue, Oct 28, 2014 at 09:29:16PM +0100, Christian Borntraeger wrote: > Am 28.10.2014 21:22, schrieb Tejun Heo: > > On Tue, Oct 28, 2014 at 09:20:55PM +0100, Christian Borntraeger wrote: > >> I have not verified this, but I guess what happens is: > >> hotplug > >> -> notify > >> -> blk_mq_queue_reinit_notify > >> -> blk_mq_queue_reinit > >> -> blk_mq_freeze_queue > >> -> percpu_ref_kill > >> -> percpu_ref_kill_and_confirm > >> -> __percpu_ref_switch_to_atomic > >> -> call_rcu_sched > > > > But call_rcu_sched() wouldn't show up as latency. It's an async call > > unlike synchronize_*(). > > Right, but > > blk_mq_freeze_queue > > also contains > > wait_event(q->mq_freeze_wq, percpu_ref_is_zero(&q->mq_usage_counter)); > > Isnt that wait_event woken up at the end of the call_rcu_sched? Yeah, yeah, I was confused. We just need to initiate the killing for all mqs at once and then wait for the completions. Shouldn't be too difficult to fix. Will get to it soon. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
