2016 IEEE International Symposium on High Performance Computer Architecture (HPCA) 2016
DOI: 10.1109/hpca.2016.7446095
|View full text |Cite
|
Sign up to set email alerts
|

Low-Cost Inter-Linked Subarrays (LISA): Enabling fast inter-subarray data movement in DRAM

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
156
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
4
3
2

Relationship

4
5

Authors

Journals

citations
Cited by 183 publications
(156 citation statements)
references
References 43 publications
0
156
0
Order By: Relevance
“…Increasing core counts, emergence of more data-intensive and latencycritical applications, and increasingly limited bandwidth in the memory system are together leading to higher memory latency. Thus, low-latency memory operation is now even more important to improving overall system performance [9,11,16,27,36,37,38,45,49,53,54,56,66,68,70,79].…”
Section: Introductionmentioning
confidence: 99%
“…Increasing core counts, emergence of more data-intensive and latencycritical applications, and increasingly limited bandwidth in the memory system are together leading to higher memory latency. Thus, low-latency memory operation is now even more important to improving overall system performance [9,11,16,27,36,37,38,45,49,53,54,56,66,68,70,79].…”
Section: Introductionmentioning
confidence: 99%
“…In a block group, the metadata block stores the sequence ID (SID), which is the unique number in the memory log area to represent a block group, and the metadata (BLK-1. Note that memory controllers are becoming increasingly more intelligent and complex to deal with various scheduling and performance management issues in multi-core and heterogeneous systems (e.g., [5], [6], [7], [8], [11], [12], [13], [14], [21], [25], [26], [27], [32], [33], [34], [35], [38], [39], [42], [45], [46], [49], [50], [51], [52], [53], [54], [61], [62], [64], [65], [66], [67], [68], [81], [84], [85], [86], [87], [88], [89], [97], [98], [108], [110], [112], [113],…”
Section: Eager Commitmentioning
confidence: 99%
“…Regardless of the exact implementation, we believe RowHammer, and other upcoming reliability vulnerabilities like RowHammer, can be much more easily found, mitigated, and prevented with better cooperation between and co-design of system and memory, i.e., system-memory co-design [77]. System-memory co-design is explored by recent works for mitigating various DRAM scaling issues, including retention failures and performance problems [68,52,77,45,79,70,46,84,48,47,63,62,91,27,28,69,26,53,65,38,93,64,92]. Taking the system-memory co-design approach further, providing more intelligence and configurability/programmability in the memory controller can greatly ease the tolerance to errors like RowHammer: when a new failure mechanism in memory is discovered, the memory controller can be configured/programmed/patched to execute specialized functions to profile and correct for such mechanisms.…”
Section: Solutions To Rowhammermentioning
confidence: 99%