aboutsummaryrefslogtreecommitdiffhomepage
path: root/content/2023-01-14-xpost-matcha-threads/index.md
diff options
context:
space:
mode:
authorJohannes Stoelp <johannes.stoelp@gmail.com>2024-12-18 21:06:55 +0100
committerJohannes Stoelp <johannes.stoelp@gmail.com>2024-12-18 21:06:55 +0100
commit4e53dc0e6b4e2928dddac12dfdd990dbfc3befa5 (patch)
treec262ee798515fc3f7eb4d070eedd25443c010bbf /content/2023-01-14-xpost-matcha-threads/index.md
parentc6a60f113001beff924fb5449cbb358d3b03ad8d (diff)
downloadblog-4e53dc0e6b4e2928dddac12dfdd990dbfc3befa5.tar.gz
blog-4e53dc0e6b4e2928dddac12dfdd990dbfc3befa5.zip
xpost: reset colors to default in figures to allow easy light/dark generation
Diffstat (limited to 'content/2023-01-14-xpost-matcha-threads/index.md')
-rw-r--r--content/2023-01-14-xpost-matcha-threads/index.md4
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.