github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-04-29 04:04:45 +00:00
Code Issues Projects Releases Wiki Activity

docs: kata 3.0 Architecture

Browse Source 
fix readme content error

Fixes: #5498
Signed-off-by: zhaoxu <zhaoxu@megvii.com>
This commit is contained in:
zhaoxu 2022-10-24 11:07:34 +08:00
parent ee189d2ebe
commit abf4f9b299
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/design/architecture_3.0/README.md
View File

@ -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 listener thread(M * tokio task)
├─ TTRPC client handler thread(7 * 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 stdin io thread(M * tokio task) └─ container stderr io thread(M * tokio task)
``` ```
### Extensible Framework ### 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. 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.