From abf4f9b2999d673e437fb5507e78147f3f15bd78 Mon Sep 17 00:00:00 2001 From: zhaoxu Date: Mon, 24 Oct 2022 11:07:34 +0800 Subject: [PATCH] docs: kata 3.0 Architecture fix readme content error Fixes: #5498 Signed-off-by: zhaoxu --- docs/design/architecture_3.0/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/design/architecture_3.0/README.md b/docs/design/architecture_3.0/README.md index 8159409489..bc0acf6b24 100644 --- a/docs/design/architecture_3.0/README.md +++ b/docs/design/architecture_3.0/README.md @@ -64,8 +64,8 @@ The kata-runtime is controlled by TOKIO_RUNTIME_WORKER_THREADS to run the OS thr ├─ TTRPC listener thread(M * tokio task) ├─ TTRPC client handler thread(7 * M * tokio task) ├─ container stdin io thread(M * tokio task) - ├─ container stdin io thread(M * tokio task) - └─ container stdin io thread(M * tokio task) + ├─ container stdout io thread(M * tokio task) + └─ container stderr io thread(M * tokio task) ``` ### Extensible Framework The Kata 3.x runtime is designed with the extension of service, runtime, and hypervisor, combined with configuration to meet the needs of different scenarios. At present, the service provides a register mechanism to support multiple services. Services could interact with runtime through messages. In addition, the runtime handler handles messages from services. To meet the needs of a binary that supports multiple runtimes and hypervisors, the startup must obtain the runtime handler type and hypervisor type through configuration.