Augustin Cavalier
763cfd171b
This way we don't need to call barrier_unlock() in every thread after exiting the wait loop, some syscalls. We can also avoid spinning on the barrier mutex in "ensure_idle" (which is renamed "ensure_none_exiting" for clarity), and instead lock it once and wait for some thread to unblock all. Overall, this strategy appears to be as much as 25% faster than the previous, testing with pthread_barrier_test. It seems the old design had at least one possible but very narrow race in the "last one out" logic: if that thread was suspended between the atomic_add() and the assignment of barrier->lock, and all three other threads then ran past the add() in the next run, then when the last-one-out woke up, it would clear the WAITING flag spuriously. This may help with #19876.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://grok.nikisoft.one/opengrok/ (OpenGrok, provided by Niklas Poslovski)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.