mirror of
https://github.com/Zenithsiz/ist-pic-report.git
synced 2026-02-03 05:57:12 +00:00
Added several TODOS.
This commit is contained in:
parent
cdcef1bf1b
commit
fb849997b0
3
.vscode/settings.json
vendored
3
.vscode/settings.json
vendored
@ -4,6 +4,7 @@
|
||||
"ftmemsim",
|
||||
"hbadness",
|
||||
"optane",
|
||||
"printbibliography"
|
||||
"printbibliography",
|
||||
"recompiler"
|
||||
]
|
||||
}
|
||||
|
||||
41
report.tex
41
report.tex
@ -5,6 +5,8 @@
|
||||
\usepackage{biblatex}
|
||||
\usepackage{hyperref}
|
||||
|
||||
% TODO: DUE DATE: 12/07
|
||||
|
||||
% `biblatex` resources
|
||||
\addbibresource{references.bib}
|
||||
|
||||
@ -23,8 +25,8 @@
|
||||
\begin{abstract}
|
||||
\end{abstract}
|
||||
|
||||
% Motivation
|
||||
\section{Motivation}
|
||||
% Introduction
|
||||
\section{Introduction}
|
||||
|
||||
Over recent years, we've witnessed the introduction of
|
||||
programs that require extremely large runtime datasets.
|
||||
@ -80,9 +82,32 @@ since they don't involve copying to/from a hard-drive or solid-state disk.
|
||||
It is also possible to, in some configurations, perform these page migrations in
|
||||
the background via a DMA command to another processing unit in the system.
|
||||
|
||||
% TODO: Explain what we're doing
|
||||
|
||||
% TODO: Problem is somewhat unresolved
|
||||
|
||||
% TODO: Mention more tired memory systems
|
||||
|
||||
% TODO: Memory systems aren't very well developed
|
||||
|
||||
% TODO: Want to contribute to this problem, by studying current systems
|
||||
|
||||
% TODO: Explain what we solved (Some HeMem results not yet studied + framework)
|
||||
|
||||
% TODO: Explain swap isn't byte-addressable
|
||||
|
||||
% TODO: Explain how heterogenous memory models address multiple RAMs (~NUMA)
|
||||
|
||||
% Background
|
||||
\section{Background}
|
||||
|
||||
% Explain how some memories systems exist
|
||||
% Hybrid:
|
||||
% TODO: Example: DRAM + Optane
|
||||
% TODO: Example: DRAM + CCLX Mention
|
||||
|
||||
% TODO: Explain how OSes interact with memory systems
|
||||
|
||||
One such implementation of a tiered-memory system is HeMem \cite{10.1145/3477132.3483550}.
|
||||
It is designed to work with two memories: A main memory based on DRAM, as well
|
||||
as secondary memory, based on Intel Optane.
|
||||
@ -107,6 +132,10 @@ The coldest memory is chosen for this migration.
|
||||
|
||||
When a hot page that resides in main memory becomes cold, it is moved to secondary memory.
|
||||
|
||||
% TODO: Mention approach 1 (JIT recompiler that checks "hot" memory sections)
|
||||
|
||||
% TODO: Mention approach 2 (Runtime, like HeMem)
|
||||
|
||||
% Objectives
|
||||
\section{Objectives}
|
||||
|
||||
@ -137,6 +166,14 @@ produce graphs to intuitively visualize the data.
|
||||
% Results
|
||||
\section{Results}
|
||||
|
||||
% TODO: Ensure replicability
|
||||
|
||||
% TODO: Mention workloads & explain them (Single-treaded versus Multi-threaded).
|
||||
|
||||
% TODO: Section should be Q&A.
|
||||
|
||||
% TODO: Add "conclusion" to each question / graph.
|
||||
|
||||
% Conclusion
|
||||
\section{Conclusion}
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user