d8914ec8b0
If the vnode's reference count is already > 0 and we can increment it from there, then we know it's already used and we don't need to run any further checks. This saves us having to acquire the vnode lock every single time we want to get the vnode. (IsBusy() doesn't use an atomic get to fetch the flags value, but as this is the first read of the value after having acquired the vnode lock, that should not be a problem.) Adjust free_vnode, while at it, to not set a positive reference count during destruction, to be fully certain nothing will see this vnode as being available for use, and add an assertion checking this. Improves "git status" time significantly, at least in the case where all vnodes are in the disk caches. This fast path also seems to be hit very many times (> 100,000) on boot, and in compile jobs, too. Change-Id: Ibcc65aecbfcdc4f3fca42baa3756e39aab8b9efb Reviewed-on: https://review.haiku-os.org/c/haiku/+/8583 Reviewed-by: waddlesplash <waddlesplash@gmail.com> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
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://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- 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.