Avoiding spill over for read-only clients
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Read-only clients like `unifyfs-ls` will write out a spill over file at the end of execution.
A temporary fix is to set both `UNIFYFS_LOGIO_SPILL_SIZE` and `UNIFYFS_LOGIO_SHMEM_SIZE` to 0 before running the read-only client.
Or maybe we can add a read-only mode of initialization, so the read-only clients can configure all parameters programmatically.
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 reproducing the spill-over file from a read-only client such as unifyfs-ls, comparing default settings with UNIFYFS_LOGIO_SPILL_SIZE and UNIFYFS_LOGIO_SHMEM_SIZE set to 0. Trace the client initialization path and determine whether a read-only initialization mode is feasible. Done means read-only clients avoid creating spill-over files without requiring those environment overrides, while normal clients retain their behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100