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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

468 bytes

Lines

21

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/atomic.h

Detected Declarations

• struct thread

Annotated Snippet

#ifndef THREAD_UTILS_H
#define THREAD_UTILS_H

#include <linux/atomic.h>

/* Thread and synchronization utilities */

struct thread;

void vdo_initialize_threads_mutex(void);
int __must_check vdo_create_thread(void (*thread_function)(void *), void *thread_data,
				   const char *name, struct thread **new_thread);
void vdo_join_threads(struct thread *thread);

#endif /* UDS_THREADS_H */

Annotation

• Immediate include surface: `linux/atomic.h`.
• Detected declarations: `struct 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.