Directory operations
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
In UnifyCR, the directory operations are only handled locally, which may cause a inconsistent status to applications. In specific, the following directory operations are expected to be implemented:
opendir(3)fdopendir(3)closedir(3)readdir(3)rewinddir(3)dirfd(3)telldir(3)scandir(3)seekdir(3)
One thing to discuss is that there might be a case where such globally-synchronized directory operations are not necessary but prefers better performance by not touching the global metadata db for directory operations. Although directory operations would not be a huge I/O bottleneck in most cases, it would be possible to make this as configurable by the consistency model that user specifies (i.e., laminated, posix, ....).
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 tracing UnifyCR’s existing local handling of directory operations, then review the listed APIs: opendir, fdopendir, closedir, readdir, rewinddir, dirfd, telldir, scandir, and seekdir. The issue does not name files or tests; completion requires deciding how these operations synchronize with global metadata and whether consistency models should control that behavior.
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