ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

scheduler.md: update static scheduler description

Browse Source 
Add a note about not supporting re-enablement of
static scheduler.

Change-Id: I073d904311a88bf812201ca2b1465dcbdc821792
Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15056
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
This commit is contained in:
Krzysztof Karas 2022-10-19 10:36:28 +00:00 committed by Tomasz Zawadzki
parent a74c8c2e8c
commit bdf42664d1
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/scheduler.md
View File

@ -59,8 +59,13 @@ schedulers in different scenarios and workloads.
The `static` scheduler is the default scheduler and does no dynamic scheduling. The `static` scheduler is the default scheduler and does no dynamic scheduling.
Lightweight threads are distributed round-robin among reactors, respecting Lightweight threads are distributed round-robin among reactors, respecting
their requested cpu_mask, and then they are never moved. This is equivalent to their requested cpu_mask, only at application startup, and then they are never
the previous behavior of the SPDK event/application framework. moved. This is equivalent to the previous behavior of the SPDK event/application
framework.
The `static` scheduler cannot be re-enabled after a different scheduler has been
selected, because currently there is no way to save original SPDK thread distribution
configuration.
### dynamic ### dynamic