From 3bcc3e70f197fefdf6a36c7561297244b189a946 Mon Sep 17 00:00:00 2001 From: Alexander Smorkalov Date: Fri, 7 Apr 2023 13:56:57 +0300 Subject: [PATCH] Extended setNumThreads documentation according to code review. --- modules/core/include/opencv2/core/utility.hpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/core/include/opencv2/core/utility.hpp b/modules/core/include/opencv2/core/utility.hpp index 5fc5a4eaac..db8c42976f 100644 --- a/modules/core/include/opencv2/core/utility.hpp +++ b/modules/core/include/opencv2/core/utility.hpp @@ -181,9 +181,9 @@ CV_EXPORTS void glob(String pattern, std::vector& result, bool recursive /** @brief OpenCV will try to set the number of threads for subsequent parallel regions. -If threads == 0, OpenCV will disable threading optimizations and run all it's functions -sequentially. Passing threads \< 0 will reset threads number to system default. This function must -be called outside of parallel region. +If threads == 1, OpenCV will disable threading optimizations and run all it's functions +sequentially. Passing threads \< 0 will reset threads number to system default. +The function is not thread-safe. It must not be called in parallel region or concurrent threads. OpenCV will try to run its functions with specified threads number, but some behaviour differs from framework: