diff options
Diffstat (limited to 'content/2023-01-14-xpost-matcha-threads/index.md')
| -rw-r--r-- | content/2023-01-14-xpost-matcha-threads/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/content/2023-01-14-xpost-matcha-threads/index.md b/content/2023-01-14-xpost-matcha-threads/index.md index a916145..bb90dfd 100644 --- a/content/2023-01-14-xpost-matcha-threads/index.md +++ b/content/2023-01-14-xpost-matcha-threads/index.md @@ -64,7 +64,7 @@ Implementations for different ISAs are available here: - [riscv64][yield-rv64] <div style="overflow: auto;"> -<img src="init-stack.svg" style="float: right; width: 20%; padding-left: 2ch;"> +<img src="init-stack.svg" style="float: right; width: 25%; padding-left: 2ch;"> Since a thread returns into the last stack-frame of the new thread after switching the stack pointers in the yield function, special care must be taken @@ -87,7 +87,7 @@ The figure below depicts *os-level* threading (left) vs *user-level* threading (right). The main difference is that in the case of user-level threading, the operating -system (os) does not now anything about the user threads. In the concrete +system (os) does not know anything about the user threads. In the concrete example, only a **single** user thread can run at any given time, whereas in the case of os-level threading, all threads can run truly parallel. |