From f5b22decbce5230714ca9ab1e02ac5cb22f53165 Mon Sep 17 00:00:00 2001 From: Amaury Chamayou Date: Wed, 31 Jul 2024 20:31:58 +0100 Subject: [PATCH] Remove experimental wording on threading in documentation (#6414) --- doc/architecture/threading.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/architecture/threading.rst b/doc/architecture/threading.rst index 18038848fae0..702a37c10f97 100644 --- a/doc/architecture/threading.rst +++ b/doc/architecture/threading.rst @@ -17,8 +17,6 @@ Implementation Configuration ~~~~~~~~~~~~~ -.. warning:: Multiple enclave threads are experimental for now. The ``worker_threads`` configuration option should be set to ``0`` in production environments. - To enable multiple worker threads, the ``worker_threads`` configuration option can be used along with the number of desired threads to ``cchost`` when starting a CCF node. It is strongly recommended that all CCF nodes run the same number of worker threads. @@ -32,4 +30,4 @@ It is strongly advised that during the execution of a command the application do Any inter-command communication must be performed via the key-value store, to ensure that CCF can rollback commands or change the primary as required. If an application has global state that exists outside the key-value store, CCF offers several concurrency control primitives (via Open Enclave) to protect memory that could be accessed concurrently by multiple threads. -It is recommended that these primitives are used rather than other primitives, such as mutexes, which may result in an OCALL. \ No newline at end of file +It is recommended that these primitives are used rather than other primitives, such as mutexes, which may result in an OCALL.