Add wrappers for aio functions
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
We have a wrapper for lio_listio(), but its implementation does not handle all I/O ops (read ops, but not write ops), nor does it support the user providing a list of ops that might mix across unifycr and system files. Additionally, we likely need wrappers for other aio functions, and we should consider how to make the implementations actually be asynchronous, e.g., start the read/write op but not block on it to complete.
In short, we need to spend some time considering aio wrappers. Or we could opt to decide to not support async I/O operations, in which case, we should probably drop our lio_listio wrapper.
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
Start by reviewing the existing lio_listio() wrapper and how it handles read operations. Compare the needs for write operations and lists mixing UnifyFS and system files, then determine whether the wrappers should provide genuinely asynchronous behavior or be removed. Done means a decided scope for aio support and corresponding implementation direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100