guide: storage: CPU affinity docs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 238
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 100
Description
Describe the high level behaviors of CPU affinity for IO. E.g. when a guest issues IO on VP n, what VP does storvsp, the disk backends, and the device backend see? What about for IDE or NVMe frontend storage? When does this fall down, and what's the behavior?
Ideally this would come after a document describing the OpenHCL executor and CPU model.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. First read the planned OpenHCL executor and CPU model documentation, then trace the storage path for guest IO on VP n across storvsp, disk backends, device backends, and IDE or NVMe frontends. Done means the documentation explains normal CPU-affinity behavior and where it breaks down.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100