+44
−1
+11
−0
+61
−0
+12
−1
+51
−2
Loading
Added new 'scheduler_set_options' RPC. 1. isolated_core_mask: Users are allowed to select cores to isolate during scheduling 2. scheduling_core: Users are allowed to select main core of scheduling This RPC can only be called before SPDK subsystems have been initialized. These parameters can only be set once. The following options are for general mechanisms. For example, dynamic scheduler now allows specific cores to be isolated from scheduling through the newly added isolated_core_mask. This means that no threads can enter or leave the cores designated as isolated cores. Core isolation can be useful in the following situation: The user may want the main core to be dedicated to orchestration tasks(such as RPCs, etc.) and does not want any IO work to be assigned to it while running dynamic scheduler. These changes allow user to dedicate main thread for RPC, assign nvmf poll groups to non-main thread cores, and then ensure that dynamic(or any other) scheduler will not place any other spdk_threads on the main core. Change-Id: Idb5e564150d014cec7106d48d609d83490561a94 Signed-off-by:SeungYeon Shin <syeon.shin@samsung.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/23156 Reviewed-by:
Jim Harris <jim.harris@samsung.com> Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Shuhei Matsumoto <smatsumoto@nvidia.com>