eclipse-iceoryx / eclipse-iceoryx/iceoryx2
Port 'SignalMechanism' from 'Semaphore' to POSIX 'ConditionVariable' where possible
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 187
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 47
Description
## Brief feature description
The `Semaphore` supports only `CLOCK_REALTIME`, which has issues when the system time is changed. The POSIX `ConditionVariable` has an attribute to specify the clock and also accepts `CLOCK_MONOTONIC`.
On Systems that support POSIX condition variables, those should be used with the `CLOCK_MONOTONIC` instead of the `Semaphore` in combination with the `AdaptiveWait`.
Contributor guide
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 locating the Rust implementations of Semaphore, AdaptiveWait, and SignalMechanism, then inspect how POSIX ConditionVariable support and clock selection are handled. Done means supported POSIX systems use a monotonic condition variable where possible instead of Semaphore with AdaptiveWait, while the issue's platform fallback behavior remains defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100