Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Menu
Open sidebar
kookiespace
talks
Concurrency data correctness and rust
Commits
2b8fab6d
Verified
Commit
2b8fab6d
authored
Oct 07, 2021
by
Katharina Fey
🏴
Browse files
Update
parent
86797f4d
Changes
1
Hide whitespace changes
Inline
Side-by-side
slides.md
View file @
2b8fab6d
...
...
@@ -2,7 +2,7 @@
transition
:
none
---
# C
u
ncurrency,
d
ata
c
orrectness, and Rust
# C
o
ncurrency,
D
ata
C
orrectness, and Rust
::: notes
...
...
@@ -10,6 +10,7 @@ Hey and welcome to my talk.
:::
---
# `whoami(1)`
...
...
@@ -70,6 +71,22 @@ jargon that I would like to explain to you first.
::: notes
It's good to keep a model of our computer in mind when writing code.
Many errors might seem obvious once we do this.
CPU: Executes instructions on cores and threads. Each thread has its
own cache with a shared cache between them.
Memory: Connected to the CPU, usually _very_ slow to access in CPU
scale time. This is why values get (and stay) cached.
Synchronising Cache and Memory is the CPUs job. We don't have to
worry. BUT: concurrent prograbs CAN break this mechanism.
:::
---
# Some examples
---
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment