From bdf42664d13c892cc1b23bd0dac109b69a63bb05 Mon Sep 17 00:00:00 2001 From: Krzysztof Karas Date: Wed, 19 Oct 2022 10:36:28 +0000 Subject: [PATCH] scheduler.md: update static scheduler description Add a note about not supporting re-enablement of static scheduler. Change-Id: I073d904311a88bf812201ca2b1465dcbdc821792 Signed-off-by: Krzysztof Karas Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15056 Tested-by: SPDK CI Jenkins Reviewed-by: Jim Harris Reviewed-by: Tomasz Zawadzki --- doc/scheduler.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/scheduler.md b/doc/scheduler.md index 3090645f9..0781532ea 100644 --- a/doc/scheduler.md +++ b/doc/scheduler.md @@ -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