346
3. Every time the application will write to the file:
a. Before the application writes data, it clears the “clean” flag in its
metadata file and ensures that the flag has been flushed to the
persistence domain.
b. Application writes data to its persistent memory space.
c. After the application completes writing data, it sets the “clean” flag
in its metadata file and ensures the flag has been flushed to the
persistence domain.
PMDK libraries make these steps significantly easier and account for interleaving set
configurations.
Summary
This chapter describes some of the RAS features that are available to persistent memory
devices and that are relevant to persistent memory applications. It should have given you
a deeper understanding of uncorrectable errors and how applications can respond to
them, how operating systems can detect health status changes to improve the availability
of applications, and how applications can best detect dirty shutdowns and use the data
loss counter.
Open Access This chapter is licensed under the terms of the Creative
Commons Attribution 4.0 International License (http://creativecommons.
org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and
reproduction in any medium or format, as long as you give appropriate credit to the
original author(s) and the source, provide a link to the Creative Commons license and
indicate if changes were made.
The images or other third party material in this chapter are included in the chapter’s
Creative Commons license, unless indicated otherwise in a credit line to the material. If
material is not included in the chapter’s Creative Commons license and your intended
use is not permitted by statutory regulation or exceeds the permitted use, you will need
to obtain permission directly from the copyright holder.
Chapter 17 reliability, availability, and ServiCeability (raS)
3. Every time the application will write to the file:
a. Before the application writes data, it clears the “clean” flag in its
metadata file and ensures that the flag has been flushed to the
persistence domain.
b. Application writes data to its persistent memory space.
c. After the application completes writing data, it sets the “clean” flag
in its metadata file and ensures the flag has been flushed to the
persistence domain.
PMDK libraries make these steps significantly easier and account for interleaving set
configurations.
Summary
This chapter describes some of the RAS features that are available to persistent memory
devices and that are relevant to persistent memory applications. It should have given you
a deeper understanding of uncorrectable errors and how applications can respond to
them, how operating systems can detect health status changes to improve the availability
of applications, and how applications can best detect dirty shutdowns and use the data
loss counter.
Open Access This chapter is licensed under the terms of the Creative
Commons Attribution 4.0 International License (http://creativecommons.
org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and
reproduction in any medium or format, as long as you give appropriate credit to the
original author(s) and the source, provide a link to the Creative Commons license and
indicate if changes were made.
The images or other third party material in this chapter are included in the chapter’s
Creative Commons license, unless indicated otherwise in a credit line to the material. If
material is not included in the chapter’s Creative Commons license and your intended
use is not permitted by statutory regulation or exceeds the permitted use, you will need
to obtain permission directly from the copyright holder.
Chapter 17 reliability, availability, and ServiCeability (raS)