dm zoned: drive-managed zoned block device target
The dm-zoned device mapper target provides transparent write access to zoned block devices (ZBC and ZAC compliant block devices). dm-zoned hides to the device user (a file system or an application doing raw block device accesses) any constraint imposed on write requests by the device, equivalent to a drive-managed zoned block device model. Write requests are processed using a combination of on-disk buffering using the device conventional zones and direct in-place processing for requests aligned to a zone sequential write pointer position. A background reclaim process implemented using dm_kcopyd_copy ensures that conventional zones are always available for executing unaligned write requests. The reclaim process overhead is minimized by managing buffer zones in a least-recently-written order and first targeting the oldest buffer zones. Doing so, blocks under regular write access (such as metadata blocks of a file system) remain stored in conventional zones,...
Showing
- Documentation/device-mapper/dm-zoned.txt 144 additions, 0 deletionsDocumentation/device-mapper/dm-zoned.txt
- drivers/md/Kconfig 17 additions, 0 deletionsdrivers/md/Kconfig
- drivers/md/Makefile 2 additions, 0 deletionsdrivers/md/Makefile
- drivers/md/dm-zoned-metadata.c 2509 additions, 0 deletionsdrivers/md/dm-zoned-metadata.c
- drivers/md/dm-zoned-reclaim.c 570 additions, 0 deletionsdrivers/md/dm-zoned-reclaim.c
- drivers/md/dm-zoned-target.c 967 additions, 0 deletionsdrivers/md/dm-zoned-target.c
- drivers/md/dm-zoned.h 228 additions, 0 deletionsdrivers/md/dm-zoned.h
Documentation/device-mapper/dm-zoned.txt
0 → 100644
drivers/md/dm-zoned-metadata.c
0 → 100644
This diff is collapsed.
drivers/md/dm-zoned-reclaim.c
0 → 100644
drivers/md/dm-zoned-target.c
0 → 100644
This diff is collapsed.
drivers/md/dm-zoned.h
0 → 100644
Please register or sign in to comment