drivers/md/dm-vdo/thread-registry.h

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-vdo/thread-registry.h

Extension

.h

Size

729 bytes

Lines

33

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

• linux/list.h
• linux/spinlock.h

Detected Declarations

• struct thread_registry
• struct registered_thread

Annotated Snippet

struct thread_registry {
	struct list_head links;
	spinlock_t lock;
};

struct registered_thread {
	struct list_head links;
	const void *pointer;
	struct task_struct *task;
};

void vdo_initialize_thread_registry(struct thread_registry *registry);

void vdo_register_thread(struct thread_registry *registry,
			 struct registered_thread *new_thread, const void *pointer);

void vdo_unregister_thread(struct thread_registry *registry);

const void *vdo_lookup_thread(struct thread_registry *registry);

#endif /* VDO_THREAD_REGISTRY_H */

Annotation

• Immediate include surface: `linux/list.h`, `linux/spinlock.h`.
• Detected declarations: `struct thread_registry`, `struct registered_thread`.
• 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.