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

loom: add abstraction for RwLock to remove poisoning aspect #6807

Merged
merged 2 commits into from
Sep 5, 2024
Merged

loom: add abstraction for RwLock to remove poisoning aspect #6807

merged 2 commits into from
Sep 5, 2024
+114 −44

Commits on Aug 30, 2024

  1. loom: add abstraction for RwLock to remove poisoning aspect 

    With tokio-rs#6779 we removed unnecessary allocations from the timerwheel by
wrapping it in an `std::sync::RwLock`. Since the `Mutex` used in this
part of the project uses an abstraction in `loom::sync::Mutex` to get
rid of the poisoning aspects of `std::sync::Mutex` the same should
probably be done for the used read-write lock struct.

This commit introduces an abstraction to get rid of the poisoning
aspects of `std::sync::RwLock` by introducing a wrapper to the
`loom::sync` module similar to `loom::sync::Mutex`.

Refs: tokio-rs#6779
    @tglane
    tglane committed Aug 30, 2024
    Configuration menu
    Copy the full SHA
    91f3f48 View commit details
    Browse the repository at this point in the history

  2. fix loom test

    @tglane
    tglane committed Aug 30, 2024
    Configuration menu
    Copy the full SHA
    e899f77 View commit details
    Browse the repository at this point in the history