From 51dade33820bb7a5be16623e4d1dc1d83ca22926 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Thu, 19 Sep 2024 20:25:21 +0200 Subject: [PATCH] docs: Fix spell checker MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit tokio is not a valid word, it seeems, so let's use `tokio`. Signed-off-by: Fabiano Fidêncio --- docs/design/architecture_3.0/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/architecture_3.0/README.md b/docs/design/architecture_3.0/README.md index a75e2a603..d6d970a54 100644 --- a/docs/design/architecture_3.0/README.md +++ b/docs/design/architecture_3.0/README.md @@ -50,7 +50,7 @@ We provide `Dragonball` Sandbox to enable built-in VMM by integrating VMM's func #### How To Support Async The kata-runtime is controlled by TOKIO_RUNTIME_WORKER_THREADS to run the OS thread, which is 2 threads by default. For TTRPC and container-related threads run in the `tokio` thread in a unified manner, and related dependencies need to be switched to Async, such as Timer, File, Netlink, etc. With the help of Async, we can easily support no-block I/O and timer. Currently, we only utilize Async for kata-runtime. The built-in VMM keeps the OS thread because it can ensure that the threads are controllable. -**For N tokio worker threads and M containers** +**For N `tokio` worker threads and M containers** - Sync runtime(both OS thread and `tokio` task are OS thread but without `tokio` worker thread) OS thread number: 4 + 12*M - Async runtime(only OS thread is OS thread) OS thread number: 2 + N