Move ps_lock out of the architecture-specific code
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 15
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
No reason for this to be in the architecture-specific code. We're having to replicate the logic, which is quite wasteful.
Example: see ps_refcnt is moved out of arch-specific code, instead just using the architecture-specific instructions.
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
Locate the architecture-specific implementation of ps_lock and compare it with how ps_refcnt was moved out while retaining architecture-specific instructions. The work is done when ps_lock's shared logic is no longer duplicated across architectures and the architecture-specific code only contains the required instructions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100