Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement Mutex::try_lock #71

Merged
merged 2 commits into from
Jun 28, 2022
Merged

Implement Mutex::try_lock #71

merged 2 commits into from
Jun 28, 2022

Commits on Jun 15, 2022

  1. Implement Mutex::try_lock 

    Without `try_lock` it was easier to justify context switches, because
acquire was a right mover (we only needed a context switch before) and
release was a left mover (we only needed a context switch after).
However, with `try_lock` that is not the case anymore. This commit
argues why we need a context switch at the end of `lock` and `try_lock`
(both in the success and failure case), and why we do not need a context
switch at the beginning of `try_lock` and `MutexGuard::drop`.
    @bkragl
    bkragl committed Jun 15, 2022
    Configuration menu
    Copy the full SHA
    4922596 View commit details
    Browse the repository at this point in the history

Commits on Jun 28, 2022

  1. Minor tweaks

    @jamesbornholt
    jamesbornholt committed Jun 28, 2022
    Configuration menu
    Copy the full SHA
    64ff2f3 View commit details
    Browse the repository at this point in the history