include/linux/workqueue_types.h
Source file repositories/reference/linux-study-clean/include/linux/workqueue_types.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/workqueue_types.h- Extension
.h- Size
- 564 bytes
- Lines
- 26
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/atomic.hlinux/lockdep_types.hlinux/timer_types.hlinux/types.h
Detected Declarations
struct workqueue_structstruct work_structstruct work_struct
Annotated Snippet
struct work_struct {
atomic_long_t data;
struct list_head entry;
work_func_t func;
#ifdef CONFIG_LOCKDEP
struct lockdep_map lockdep_map;
#endif
};
#endif /* _LINUX_WORKQUEUE_TYPES_H */
Annotation
- Immediate include surface: `linux/atomic.h`, `linux/lockdep_types.h`, `linux/timer_types.h`, `linux/types.h`.
- Detected declarations: `struct workqueue_struct`, `struct work_struct`, `struct work_struct`.
- Atlas domain: Core OS / Core Kernel Interface.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.