include/linux/relay.h

Source file repositories/reference/linux-study-clean/include/linux/relay.h

File Facts

System: Linux kernel
Corpus path: include/linux/relay.h
Extension: .h
Size: 8749 bytes
Lines: 299
Domain: Core OS
Bucket: Core Kernel Interface
Inferred role: Core OS: operation-table or driver-model contract
Status: pattern implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

linux/types.h
linux/sched.h
linux/timer.h
linux/wait.h
linux/list.h
linux/irq_work.h
linux/bug.h
linux/fs.h
linux/poll.h
linux/kref.h
linux/percpu.h

Detected Declarations

struct rchan_buf_stats
struct rchan_buf
struct rchan
struct rchan_callbacks
function __relay_write
function relay_write
function subbuf_start_reserve

Annotated Snippet

extern const struct file_operations relay_file_operations;

#ifdef CONFIG_RELAY
int relay_prepare_cpu(unsigned int cpu);
#else
#define relay_prepare_cpu     NULL
#endif

#endif /* _LINUX_RELAY_H */

Annotation

Immediate include surface: `linux/types.h`, `linux/sched.h`, `linux/timer.h`, `linux/wait.h`, `linux/list.h`, `linux/irq_work.h`, `linux/bug.h`, `linux/fs.h`.
Detected declarations: `struct rchan_buf_stats`, `struct rchan_buf`, `struct rchan`, `struct rchan_callbacks`, `function __relay_write`, `function relay_write`, `function subbuf_start_reserve`.
Atlas domain: Core OS / Core Kernel Interface.
Implementation status: pattern 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.