block/blk-ioprio.c
Source file repositories/reference/linux-study-clean/block/blk-ioprio.c
File Facts
- System
- Linux kernel
- Corpus path
block/blk-ioprio.c- Extension
.c- Size
- 4924 bytes
- Lines
- 180
- Domain
- Representative Device Path
- Bucket
- PCIe NVMe Storage Path
- Inferred role
- Representative Device Path: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
- Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/blk-mq.hlinux/blk_types.hlinux/kernel.hlinux/module.hblk-cgroup.hblk-ioprio.hblk-rq-qos.h
Detected Declarations
struct ioprio_blkcgenum prio_policyfunction ioprio_blkcg_from_cssfunction ioprio_show_prio_policyfunction ioprio_set_prio_policyfunction ioprio_free_cpdfunction blkcg_set_iopriofunction ioprio_initfunction ioprio_exitmodule init ioprio_init
Annotated Snippet
module_init(ioprio_init);
module_exit(ioprio_exit);Annotation
- Immediate include surface: `linux/blk-mq.h`, `linux/blk_types.h`, `linux/kernel.h`, `linux/module.h`, `blk-cgroup.h`, `blk-ioprio.h`, `blk-rq-qos.h`.
- Detected declarations: `struct ioprio_blkcg`, `enum prio_policy`, `function ioprio_blkcg_from_css`, `function ioprio_show_prio_policy`, `function ioprio_set_prio_policy`, `function ioprio_free_cpd`, `function blkcg_set_ioprio`, `function ioprio_init`, `function ioprio_exit`, `module init ioprio_init`.
- Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
- Implementation status: integration 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.