NAND copyback
NAND copyback relocates page data through an on-chip buffer to a destination page without transferring the payload to an external controller.
The studied implementations constrain source and destination placement; a host copy command does not establish that NAND copyback occurred. Bypassing controller ECC can preserve read errors in the new copy, so the correction path must be specified.
Relations
- related
- nand-flash, garbage-collection, write-amplification, ftl, ldpc, data-retention
Advantages
- Can avoid the off-chip payload transfers used by a controller-mediated relocation. [2]
Limitations
- Placement restrictions are device-specific; historical odd/even rules must not be applied to every NAND generation. [2]
- Restricted-copyback research uses conditional consecutive-copy budgets, not a universal safe count. [1]
Citations
- Hong, Kim, Park, Jung and Kim. Revitalizing Copybacks in Modern SSDs: Why and How. Author manuscript arXiv:1810.04603v1, 2018, sections 3-5.
- Hu, Jiang, Feng, Tian, Luo and Zhang. Performance Impact and Interplay of SSD Parallelism through Advanced Commands, Allocation Strategy and Data Granularity. ICS 2011, sections 2.2 and 4.3.
- Han, Gwak, Shin and Hwang. ZNS+: Advanced Zoned Namespace Interface for Supporting In-Storage Zone Compaction. OSDI 2021, sections 2.1 and 3.3.1.
- Hesela: NAND copyback, faster relocation is not fewer writes
- Hesela illustrative copyback payload accounting: assumptions, results and model hash