drivers/md/dm-vdo/Kconfig
Source file repositories/reference/linux-study-clean/drivers/md/dm-vdo/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/md/dm-vdo/Kconfig- Extension
[no extension]- Size
- 457 bytes
- Lines
- 19
- Domain
- Driver Families
- Bucket
- drivers/md
- Inferred role
- Driver Families: build/configuration rule
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: GPL-2.0-only
config DM_VDO
tristate "VDO: deduplication and compression target"
depends on 64BIT
depends on BLK_DEV_DM
select DM_BUFIO
select LZ4_COMPRESS
select LZ4_DECOMPRESS
select MIN_HEAP
help
This device mapper target presents a block device with
deduplication, compression and thin-provisioning.
To compile this code as a module, choose M here: the module will
be called dm-vdo.
If unsure, say N.
Annotation
- Atlas domain: Driver Families / drivers/md.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.