drivers/md/dm-vdo

VDO Device-Mapper Deduplication and Compression Target

VDO (Virtual Data Optimizer) is a software block-layer feature that sits on top of any storage device and transparently deduplicates and compresses the data written to it. Originally developed by Permabit, acquired by Red Hat in 2017, and merged into the mainline kernel in 6.9 (2024), it is commonly used on enterprise Linux to shrink the footprint of VM images, container storage, and backups.

not-a-driver conf=1.00 deploy=none replacement=none subsystem=md category=not-a-driver
100%

recommendation

This is not actually a hardware driver directory; it is a device-mapper target that provides inline deduplication and compression as a pure-software storage feature. It is a recently merged, actively maintained Red Hat component and the question of hardware obsolescence does not apply.

repository signals

109 files
52,456 source lines
186 commits, 5y
+62,161 / −9,630 lines added / removed, 5y
23 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 186 total · active in 22/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 5 commits · +104 −108 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 44 commits · +54,702 −1,471 2023-12: 1 commit · +5 −2 2024-01: 16 commits · +3,306 −280 2024-02: 65 commits · +3,235 −7,083 2024-03: 5 commits · +21 −89 2024-04: 3 commits · +5 −5 2024-05: 5 commits · +19 −26 2024-06: 0 commits · +0 −0 2024-07: 8 commits · +113 −31 2024-08: 1 commit · +0 −1 2024-09: 4 commits · +13 −12 2024-10: 7 commits · +35 −116 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 2 commits · +4 −12 2025-02: 9 commits · +270 −160 2025-03: 0 commits · +0 −0 2025-04: 1 commit · +1 −1 2025-05: 2 commits · +14 −12 2025-06: 0 commits · +0 −0 2025-07: 1 commit · +1 −2 2025-08: 0 commits · +0 −0 2025-09: 3 commits · +6 −17 2025-10: 1 commit · +1 −1 2025-11: 1 commit · +298 −169 2025-12: 1 commit · +2 −2 2026-01: 1 commit · +6 −30 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

No sources cited.

codex reasoning notes (technical)

Not a driver directory: dm-vdo is a device-mapper VDO software block target (dedupe/compression), not kernel-bound hardware driver code.