+3
−17
Loading
There are no remaining events that require running in an spdk_thread context, so remove that code so that spdk_events are explicitly *not* called from an spdk_thread context. This is the desired behavior, there should be a clear delineation between reactor context and spdk_thread context, and this change ensures that we can send events that will not be run in an spdk_thread context. So now spdk_reactor_set_interrupt_mode() checks that it was called on the scheduling reactor, and not from the context of an spdk_thread. This also requires changing the interrupt_tgt's reactor_set_interrupt_mode RPC that is used for testing purposes. That RPC would just call spdk_reactor_set_interrupt_mode() from its spdk_thread context, but we need to use spdk_event_call() instead so that it gets called from reactor context. Signed-off-by:Jim Harris <jim.harris@samsung.com> Signed-off-by:
syeon.shin <syeon.shin@samsung.com> Change-Id: Iadfae6f0943ad77076ffb8e81e5154d998e7a6f4 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/23261 Reviewed-by:
Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-by:
Changpeng Liu <changpeng.liu@intel.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com> Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com>