...
This commit is contained in:
parent
8a7d5e7e5a
commit
dbc01147fd
3 changed files with 44 additions and 0 deletions
|
|
@ -432,3 +432,22 @@
|
||||||
author={Manson, Jeremy and Goetz, Brian},
|
author={Manson, Jeremy and Goetz, Brian},
|
||||||
year={2004}
|
year={2004}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
@inproceedings{Pinto_etal.Thymesisflow.2020,
|
||||||
|
title={Thymesisflow: A software-defined, hw/sw co-designed interconnect stack for rack-scale memory disaggregation},
|
||||||
|
author={Pinto, Christian and Syrivelis, Dimitris and Gazzetti, Michele and Koutsovasilis, Panos and Reale, Andrea and Katrinis, Kostas and Hofstee, H Peter},
|
||||||
|
booktitle={2020 53rd Annual IEEE/ACM International Symposium on Microarchitecture (MICRO)},
|
||||||
|
pages={868--880},
|
||||||
|
year={2020},
|
||||||
|
organization={IEEE}
|
||||||
|
}
|
||||||
|
|
||||||
|
@inproceedings{Couceiro_etal.D2STM.2009,
|
||||||
|
title={D2STM: Dependable distributed software transactional memory},
|
||||||
|
author={Couceiro, Maria and Romano, Paolo and Carvalho, Nuno and Rodrigues, Lu{\'\i}s},
|
||||||
|
booktitle={2009 15th IEEE Pacific Rim International Symposium on Dependable Computing},
|
||||||
|
pages={307--313},
|
||||||
|
year={2009},
|
||||||
|
organization={IEEE}
|
||||||
|
}
|
||||||
|
|
||||||
|
|
|
||||||
Binary file not shown.
|
|
@ -487,7 +487,31 @@ parallel access to shared memory on top of program order guarantees to explicate
|
||||||
program behavior under shared memory parallel programming across underlying
|
program behavior under shared memory parallel programming across underlying
|
||||||
implementations.
|
implementations.
|
||||||
|
|
||||||
|
Related to the definition of a consistency model is the coherence problem, which
|
||||||
|
arises whenever multiple actors have access to multiple copies of some datum,
|
||||||
|
which needs to be synchronized across multiple actors with regards to
|
||||||
|
write-accesses \cite{Nagarajan_etal.Primer_consistency_coherence_arch.2ed.2020}.
|
||||||
|
While less relevant to programming language design, coherence must be maintained
|
||||||
|
via a coherence protocol
|
||||||
|
\cite{Nagarajan_etal.Primer_consistency_coherence_arch.2ed.2020} in systems of
|
||||||
|
both microarchitectural and network scales. For DSM systems, the design of a
|
||||||
|
correct and performant coherence protocol is of especially high priority and
|
||||||
|
is a major part of many studies in DSM systems throughout history
|
||||||
|
\cites{Carter_Bennett_Zwaenepoel.Munin.1991}{Amza_etal.Treadmarks.1996}
|
||||||
|
{Pinto_etal.Thymesisflow.2020}{Endo_Sato_Taura.MENPS_DSM.2020}
|
||||||
|
{Couceiro_etal.D2STM.2009}.
|
||||||
|
|
||||||
|
\subsection{Common Consistency Models}
|
||||||
|
% ... should I even write this section? imo it's too basic for anyone to read
|
||||||
|
% and really just serves as a means to increase word count
|
||||||
|
|
||||||
\subsection{Consistency Model in DSM}
|
\subsection{Consistency Model in DSM}
|
||||||
|
While distributed shared memory systems with node-local caching naturally
|
||||||
|
implies the existence of a corresponding memory model, only a subset of DSM
|
||||||
|
studies (cites\dots) characterize their own system to one of the few well-known memory
|
||||||
|
models
|
||||||
|
|
||||||
|
Notably, \dots % about Munin to Spark to access-pattern vs. consistency
|
||||||
|
|
||||||
\subsection{Coherence Protocol}
|
\subsection{Coherence Protocol}
|
||||||
|
|
||||||
|
|
@ -497,6 +521,7 @@ implementations.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
(I need to read more into this. Most of the contribution comes from CPU caches,
|
(I need to read more into this. Most of the contribution comes from CPU caches,
|
||||||
less so for DSM systems.) \textbf{[Talk about JIAJIA and Treadmark's coherence
|
less so for DSM systems.) \textbf{[Talk about JIAJIA and Treadmark's coherence
|
||||||
protocol.]}
|
protocol.]}
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue