Kyungjun Lee
ABSTRACT
The adoption of non-volatile memory as main memory has recently been proposed in computer architecture community, expecting many aspects of computer systems to be changed. One of the noticeable prospects is that a cache flush could play a major role to ensure data consistency in the proposing architecture. We investigate clush and epoch barrier in order to take account of compatibility of those mechanisms with the new architecture. Our simulation shows that clush requires 128ms to complete our 64M workload, corresponding to 197% raises in execution time compared to the baseline performance. Additionally, it takes 73ms to execute the same workload with epoch barrier, which indicates that the epoch mechanism slows the performance down by 69%. Although utilizing the epoch method seems to decelerate less than using clush, it could potentially induce system degradation due to the fact that it occasionally provokes a number of write-back operations at once. This evaluation is expected to help guide further studies on reliability mechanisms in the upcoming system.
- Intel® 64 and ia-32 architectures software developer's manual. {online} http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html.Google Scholar
- Performance analysis guide for intel® core™ i7 processor and intel® xeon™ 5500 processors. {online} https://software.intel.com/sites/products/collateral/hpc/vtune/performance_analysis_guide.pdf.Google Scholar
- K. Bailey, L. Ceze, S. D. Gribble, and H. M. Levy. Operating system implications of fast, cheap, non-volatile memory. In the 13th USENIX conference on Hot topics in operating systems (HotOS-13), pages 2--2, April 2011. Google ScholarDigital Library
- J. Condit, E. B. Nightingale, C. Frost, E. Ipek, B. Lee, D. Burger, and D. Coetzee. Better I/O through byte-addressable, persistent memory. In Proceedings of the 22nd ACM Symposium on Operating Systems Principles (SOSP), 2009. Google ScholarDigital Library
- A. Driskill-Smith. Latest advances and future prospects of stt-ram. In Non-Volatile Memories Workshop, 2010.Google Scholar
- H. Kang and J. L. Wong. vcsimx86: a cache simulation framework for x86 virtualization hosts. Stony Brook University.Google Scholar
- Z. Wang, S. Shan, T. Cao, J. Gu, Y. Xu, S. Mu, Y. Xie, and D. A. Jiménez. Wade: Writeback-aware dynamic cache management for nvm-based main memory system. ACM Transactions on Architecture and Code Optimization (TACO), 10(4):51, 2013. Google ScholarDigital Library
- J. Zhao, S. Li, D. H. Yoon, Y. Xie, and N. P. Jouppi. Kiln: closing the performance gap between systems with and without persistence support. In Proceedings of the 46th Annual IEEE/ACM International Symposium on Microarchitecture, pages 421--432. ACM, 2013. Google ScholarDigital Library
Index Terms
- Performance implications of cache flushes for non-volatile memory file systems
Recommendations
Redesign the Memory Allocator for Non-Volatile Main Memory
Special Issue on Hardware and Algorithms for Learning On-a-chip and Special Issue on Alternative Computing SystemsThe non-volatile memory (NVM) has the merits of byte-addressability, fast speed, persistency and low power consumption, which make it attractive to be used as main memory. Commonly, user process dynamically acquires memory through memory allocators. ...
In-memory file system for non-volatile memory
RACS '13: Proceedings of the 2013 Research in Adaptive and Convergent SystemsCurrent memory system hierarchy consists of cache memory, main memory, and secondary storage. Each level in this hierarchy has a different access speed to tolerate the long latency of the lower level but supports a large capacity as a whole memory ...
Falcon: Fast OLTP Engine for Persistent Cache and Non-Volatile Memory
SOSP '23: Proceedings of the 29th Symposium on Operating Systems PrinciplesNon-volatile memory(NVM) has the properties of both byte addressable and persistence, which provides new opportunities for building on-line transaction processing (OLTP) engines. Recently, a new feature called eADR puts CPU cache also in the ...
Comments