Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lecture materials
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
generic software skills
lecture materials
Commits
3c911dc5
Commit
3c911dc5
authored
9 months ago
by
Dominik Zobel
Browse files
Options
Downloads
Patches
Plain Diff
More details on available and unavailable data slides
parent
147c9777
No related branches found
Branches containing commit
No related tags found
1 merge request
!74
Memory hierarchies lecture
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
lectures/memory-hierarchies/slides.qmd
+94
-9
94 additions, 9 deletions
lectures/memory-hierarchies/slides.qmd
with
94 additions
and
9 deletions
lectures/memory-hierarchies/slides.qmd
+
94
−
9
View file @
3c911dc5
...
...
@@ -283,17 +283,29 @@ T_{avg,s} &= H_1 T_1 + ((1-H_1)\cdot H_2)\cdot(T_1+T_2)\\
##
Unavailable data (1/2)
##
If data is not available in the current memory level {.leftalign}
If data is not available in the current memory level
- register spilling
- register spilling (register -> cache)
- cache missing (cache -> main memory)
- page fault (main memory -> disk)
:::{.smaller}
_Register has to look for the data in the L1 cache_
:::
- cache miss
:::{.smaller}
_The current cache has to fetch the data from the next cache or main memory_
:::
- page fault
:::{.smaller}
_Data was not found in main memory and has to be loaded from disk_
:::
## Unavailable data (2/2)
## Requesting unavailable data
:::{.r-stack}
...
...
@@ -310,18 +322,65 @@ If data is not available in the current memory level
:::
::::::::{.columns .leftalign}
:::{.column width=50%}
:::{.fragment width=100% fragment-index=2}
- Sending request
:::
:::{.fragment width=100% fragment-index=3}
- If needed, forward request until found
:::
:::
:::{.column width=50%}
:::{.fragment width=100% fragment-index=4}
## Available data (1/2
)
- Load data into cache(s
)
Techniques to provide data ahead of time
:::
:::{.fragment width=100% fragment-index=5}
- Process available data
:::
:::
::::::::
## Provide data which might be needed {.leftalign}
- caching
:::{.smaller}
_Keep data around which was needed once_
:::
- prefetching
:::{.smaller}
_Load data which might be needed soon (spatial or temporal proximity, heuristics)_
:::
- branch prediction
:::{.smaller}
_Similar to prefetching, load data needed for different code paths_
:::
##
Available data (2/2)
##
Use cached data
:::{.r-stack}
...
...
@@ -333,6 +392,32 @@ Techniques to provide data ahead of time
:::
::::::::{.columns .leftalign}
:::{.column width=50%}
:::{.fragment width=100% fragment-index=2}
- Sending request
- Data is already present
:::
:::
:::{.column width=50%}
:::{.fragment width=100% fragment-index=3}
- Load data into cache
- Process it
:::
:::
::::::::
# Memory hierarchy on Levante
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment