Power Management of Hybrid DRAM/PRAM-Based Main Memory
0.ABSTRACT
(1)non-volatile memory——low standby power
DRAM——high performance and better active power
(2)we:
present a runtime-adaptive method of DRAM decay——reduce DRAM refresh energy (large
standby power due to refresh)
present two methods——DRAM bypass and dirty data keeping—— reduction in refresh energy and memory access latency
1.Introduction
(1) In the hybrid main memory:
DRAM works as—— a cache( lower latency and smaller power consumption in
read and write than PRAM)
PRAM works as——a large background main memory(low standby power )
(2)if a memory access request to DRAM gives a miss, the data are fetched
from PRAM to DRAM and sent to the core which issued the request.
(3)in order to reduce DRAM refresh energy, in our work, data in DRAM decay over time(popular method)
2.Related Work
(1)Existing
one to exploit low power modes——maximally utilize low power modes;
the other to minimize refresh power—— (1) minimizing the number of rows to be refreshed while having the typical refresh period of 64ms, (2) maximizing refresh period (e.g., a refresh period of 128ms or 256ms)
3.Preliminaries
?
Note that a newly allocated DRAM row (the one which receives valid data from PRAM) can serve requests for 64ms without refresh.It is because data copy from PRAM to DRAM performs ACT and PRE commands to the row. Thus, the contents in the row can remain valid for 64ms without any additional DRAM refresh.
4.Basic Idea
We present three ideas for the power management of hybrid DRAM/PRAM main memory.
-
Runtime-adaptive time out control to minimize the total energy of DRAM and PRAM while meeting the given
performance constraint set by the designer(we propose a sampling-based method of dynamic TO adjustment.)
-
Bypassing DRAM to exploit the cases of reading data with low spatial locality
-
Applying a long time out to dirty data to exploit write coalescing thereby reducing PRAM writes(we propose keeping dirty data in DRAM for a longer period than clean data)
5.Proposed Power Management
?
5.1 V,C,D
6.Experiments
7.Conclusion
最新文章
- python的错误和异常
- jsp2.0+中的标签文件,JSP Fragment技术
- [双连通分量] POJ 3694 Network
- magento additional &; details 分解开来
- URAL 1167. Bicolored Horses (DP)
- Activity Recognition行为识别
- Java问题汇集(1)
- VS2010皮肤控件介绍
- 实战 SSH 端口转发
- JAVA小项目之摇奖机
- MySQL利用binlog来恢复数据库
- Swift3中如何为Array写一个限定Type的扩展
- laravel之数据库
- Vue系列之 =>; webpack的url loader
- ios开启双重认证之填坑式教学
- 用Spring Boot去创建web service
- 疯狂Workflow讲义——基于Activiti的工作流应用开 PDF 下载
- day63 django-模板语言
- idea中Hibernate反向生成工具
- firedac数据集数据序列为JSON
热门文章
- Idea使用Lombok简化实体类代码
- [Luogu] 选择客栈
- HDU3501 Calculation 2 [欧拉函数]
- 安装conda后取消命令行前出现的base,取消每次启动自动激活conda的基础环境, 使用ubuntu 自带的Python环境
- JsonObject处理时间转换问题
- Java写入的常用技巧(二)
- Leetcode题目分类整理
- Leetcode题目215.数组中的第K个最大元素(中等)
- Mac下mysql服务端密码重置及环境配置
- dts是如何来描述iommu与PCI(e)之间的关系?