io_uring/loop.h
Source file repositories/reference/linux-study-clean/io_uring/loop.h
File Facts
- System
- Linux kernel
- Corpus path
io_uring/loop.h- Extension
.h- Size
- 689 bytes
- Lines
- 38
- Domain
- Kernel Services
- Bucket
- io_uring
- Inferred role
- Kernel Services: implementation source
- Status
- source implementation candidate
Why This File Exists
Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/io_uring_types.h
Detected Declarations
struct iou_loop_paramsfunction io_has_loop_ops
Annotated Snippet
struct iou_loop_params {
/*
* The CQE index to wait for. Only serves as a hint and can still be
* woken up earlier.
*/
__u32 cq_wait_idx;
};
enum {
IOU_LOOP_CONTINUE = 0,
IOU_LOOP_STOP,
};
static inline bool io_has_loop_ops(struct io_ring_ctx *ctx)
{
return data_race(ctx->loop_step);
}
int io_run_loop(struct io_ring_ctx *ctx);
static inline struct iou_ctx *io_loop_mangle_ctx(struct io_ring_ctx *ctx)
{
return (struct iou_ctx *)ctx;
}
static inline struct io_ring_ctx *io_loop_demangle_ctx(struct iou_ctx *ctx)
{
return (struct io_ring_ctx *)ctx;
}
#endif
Annotation
- Immediate include surface: `linux/io_uring_types.h`.
- Detected declarations: `struct iou_loop_params`, `function io_has_loop_ops`.
- Atlas domain: Kernel Services / io_uring.
- 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.