drivers/md/dm-vdo/flush.h
Source file repositories/reference/linux-study-clean/drivers/md/dm-vdo/flush.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/md/dm-vdo/flush.h- Extension
.h- Size
- 1181 bytes
- Lines
- 45
- Domain
- Driver Families
- Bucket
- drivers/md
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
funnel-workqueue.htypes.hvio.hwait-queue.h
Detected Declarations
struct vdo_flushstruct flusher
Annotated Snippet
struct vdo_flush {
/* The completion for enqueueing this flush request. */
struct vdo_completion completion;
/* The flush bios covered by this request */
struct bio_list bios;
/* The wait queue entry for this flush */
struct vdo_waiter waiter;
/* Which flush this struct represents */
sequence_number_t flush_generation;
};
struct flusher;
int __must_check vdo_make_flusher(struct vdo *vdo);
void vdo_free_flusher(struct flusher *flusher);
thread_id_t __must_check vdo_get_flusher_thread_id(struct flusher *flusher);
void vdo_complete_flushes(struct flusher *flusher);
void vdo_dump_flusher(const struct flusher *flusher);
void vdo_launch_flush(struct vdo *vdo, struct bio *bio);
void vdo_drain_flusher(struct flusher *flusher, struct vdo_completion *completion);
void vdo_resume_flusher(struct flusher *flusher, struct vdo_completion *parent);
#endif /* VDO_FLUSH_H */
Annotation
- Immediate include surface: `funnel-workqueue.h`, `types.h`, `vio.h`, `wait-queue.h`.
- Detected declarations: `struct vdo_flush`, `struct flusher`.
- Atlas domain: Driver Families / drivers/md.
- Implementation status: source implementation candidate.
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.