+0
−6
Loading
poller_set_interrupt_mode() only can be called when spdk_interrupt_mode_is_enabled() is true. But when spdk_interrupt_mode_is_enabled() is true, we also know that all pollers will have their set_intr_cb_fn set: - spdk_poller_register() will set a default ->set_intr_cb_fn when spdk_interrupt_mode_is_enabled() == true - if spdk_poller_register_interrupt() is later called on that poller, it must specify a ->set_intr_cb_fn So checking poller->set_intr_cb_fn in poller_set_interrupt_mode() is pointless, it will always be set. If we want to have warnings for cases where interrupt mode is enabled, but there are busy pollers that haven't been registered for interrupts, we need some other mechanism. Remove this mechanism that seemed to be trying to do this, but clearly doesn't. Signed-off-by:Jim Harris <jim.harris@samsung.com> Change-Id: I033f31269e896a7c6b22a8c065b229e289510271 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24625 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by:
Changpeng Liu <changpeliu@tencent.com> Reviewed-by:
Boris Glimcher <Boris.Glimcher@emc.com> Reviewed-by:
Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by:
Krzysztof Goreczny <krzysztof.goreczny@dell.com>