Open-channel SSD

An open-channel solid state drive is a solid-state drive which does not have a firmware Flash Translation Layer implemented on the device, but instead leaves the management of the physical solid-state storage to the computer's operating system.[1][2] The Linux 4.4 kernel is an example of an operating system kernel that supports open-channel SSDs which follow the NVM Express specification. The interface used by the operating system to access open-channel solid state drives is called LightNVM.[3][4][5]

NAND Flash Characteristics

Since SSDs use NAND flash memory for storing data, it is important to understand the characteristics of this medium. NAND flash provides a read/write/erase interface. A NAND package is organized into a hierarchy of dies, planes, blocks and pages. There may be one or several dies within a single physical package. A die allows a single I/O command to be executed at a time. A plane allows similar flash commands to be executed in parallel within a die. There are three fundamental programming constraints that apply to NAND: (i) a write command must always contain enough data to program one (or several) full flash page(s), (ii) writes must be sequential within a block, and (iii) an erase must be performed before a page within a block can be (re)written. The number of program/erase (PE) cycles is limited. Because of these constraints SSD controllers write data to NAND flash memory in another order than the logical block order. This implies that the SSD controller must maintain a mapping table from host (logical) to NAND (physical) addresses. This mapping is usually called the L2P table. The layer that performs the translation from logical to physical addresses is called the flash translation layer or FTL.[6]

Comparison with Traditional SSDs

Open Channel SSDs provide more flexibility with regard to data placement decisions, overprovisioning, scheduling, garbage collection and wear leveling.[7] Open-Channel SSDs can, however, not be considered a uniform class of devices, as critical device characteristics such as minimum unit of read and minimum unit of write varies from device to device.[8] One can therefore not design an FTL that automatically works on all Open-Channel SSDs.

Traditional SSDs maintain the L2P table in DRAM on the SSD and use their own CPU for maintaining that L2P table. With Open Channel SSDs the L2P table is stored in host memory and the host CPU maintains that table. While the Open Channel SSD approach is more flexible, a significant amount of host memory and host CPU cycles is required for L2P management. With an average write size of 4 KB, almost 3 GB RAM is required for an SSD with a size of 1 TB.[9]

File Systems for Open-Channel SSDs

With open-channel SSDs, the L2P mapping can be directly integrated or merged with storage management in file systems.[10] This avoids the redundancy between system software and SSD firmware, and thus improves performance and endurance. Further, open-channel SSDs enables more flexible control over flash memory. The internal parallelism is exploited by coordinating the data layout, garbage collection and request scheduling of both system software and SSD firmware to remove the conflicts, and thus improves and smooths the performance.[11]

gollark: It was backed up. It's just that my backup retention policy was broken.
gollark: This latest messup was probably mostly on me (really should test stuff better), but I have no idea how big modded servers run without exploding.
gollark: This is really awful. I've managed to recover *some* of the new region files (from the corrupted forge-side backup), I think all the nether/end, and the level.dat, but no playerdata. Kind of annoyed at myself for misconfiguring the backup thing... anyway, if anyone has suggestions for getting more data out, or wants their own copy of stuff, you can ask, but I'm going to shut it down.
gollark: It autorestarts, that wouldn't help.
gollark: I'm going to try and run a file recovery thing on the disk now, then try and fix the zip, and if neither works guess it's an older version or ***DOOM***.

References
  1. Matias Bjørling (March 12, 2015). "Open-Channel Solid State Drives" (PDF).
  2. Lu, Youyou; Shu, Jiwu; Zheng, Weimin (2013). "Extending the Lifetime of Flash-based Storage through Reducing Write Amplification from File Systems" (PDF).
  3. Corbet, Jonathan (22 April 2015). "Taking control of SSDs with LightNVM". Retrieved 3 February 2019.
  4. Michael Larabel (15 November 2015). "A Look At The New Features Of The Linux 4.4 Kernel". Phoronix.
  5. Michael Larabel (3 November 2015). "LightNVM Support Is Going Into Linux 4.4". Phoronix.
  6. Bjørling, Matias; Gonzalez, Javier; Bonnet, Philippe (2017). LightNVM: The Linux Open-Channel SSD Subsystem (PDF). USENIX FAST. pp. 359–374.
  7. Bjørling, Matias (12 March 2015). "Open-Channel Solid State Drives" (PDF). Retrieved 3 February 2019.
  8. Picoli, Ivan Luiz; Hedam, Niclas; Bonnet, Philippe; Tözün, Pınar (12 January 2020). "Open-Channel SSD (What is it Good For)" (PDF). Retrieved 4 March 2020.
  9. "Fusion ioMemory™ VSL® 3.2.15" (PDF). SanDisk, a Western Digital Brand. Retrieved 3 February 2019.
  10. Lu, Youyou; Shu, Jiwu; Zheng, Weimin (2013). "Extending the Lifetime of Flash-based Storage through Reducing Write Amplification from File Systems" (PDF).
  11. Zhang, Jiacheng; Shu, Jiwu; Lu, Youyou (2016). "ParaFS: A Log-Structured File System to Exploit the Internal Parallelism of Flash Devices" (PDF).
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.