RwLock: Priority policy
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
It would be nice to be able to specify writer preference or reader preference.
Just using os defaults is a very bad idea in my opinión. It would be better to first enforce a default policy regardless of os, and allow changing it. Otherwise, we end up with wildly varying performance results (Like https://fy.blackhats.net.au/blog/html/2018/10/19/rust_rwlock_and_mutex_performance_oddities.html and https://www.slideshare.net/mobile/mitsunorikomatsu/performance-comparison-of-mutex-rwlock-and-atomic-types-in-rust ) and in the worst case, writer starvation.
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
The issue names no repository files, tests, or entry points. Start by reviewing the RwLock API and the linked performance reports, then define the default and configurable reader/writer policy and its acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100