Commit bdf42664 authored by Krzysztof Karas's avatar Krzysztof Karas Committed by Tomasz Zawadzki
Browse files

scheduler.md: update static scheduler description 



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

Change-Id: I073d904311a88bf812201ca2b1465dcbdc821792
Signed-off-by: default avatarKrzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15056


Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
parent a74c8c2e

doc/scheduler.md

+7 −2
Original line number Diff line number Diff line
@@ -59,8 +59,13 @@ schedulers in different scenarios and workloads. 


The `static` scheduler is the default scheduler and does no dynamic scheduling.

Lightweight threads are distributed round-robin among reactors, respecting

their requested cpu_mask, and then they are never moved. This is equivalent to

the previous behavior of the SPDK event/application framework.

their requested cpu_mask, only at application startup, and then they are never

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