Update Rust crate oxide-tokio-rt to 0.1.4#712
Open
oxide-renovate[bot] wants to merge 1 commit intomainfrom
Open
Update Rust crate oxide-tokio-rt to 0.1.4#712oxide-renovate[bot] wants to merge 1 commit intomainfrom
oxide-renovate[bot] wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.1.3→0.1.4Release Notes
oxidecomputer/oxide-tokio-rt (oxide-tokio-rt)
v0.1.4Compare Source
Summary
This updates our minimum Tokio version to 1.52.0. This allows us to
pick up two major fixes that will change our default runtime
configuration:
Tokio PR tokio-rs/tokio#7431, released in 1.51.0, changes the
multi-threaded runtime to allow tasks in the LIFO slot to participate in
work-stealing. Therefore, it should no longer be necessary to disable
the LIFO slot optimization, as the pathology where a task placed in the
LIFO slot can become permanently or semi-permanently stuck while the
task that notified them runs for a long time without yielding can no
longer occur.
Tokio PR tokio-rs/tokio#8010, released in 1.52.0,
which adds eager handoff for the I/O and time drivers in the multi-threaded
runtime. This is currently an experimental feature, although it is your
author's opinion that this is really a fix for incorrect runtime behavior. It
changes worker threads in the multi-threaded runtime to wake another
worker prior to polling tasks if that worker had previously been parked
on the I/O driver or timer wheel. Eagerly handing off these resources
should prevent pathologies such as omicron#9619.
After updating Tokio, PR #7 changed the default runtime settings to
stop disabling the LIFO slot optimization, and enable eager driver
hand-off.
What's Changed
New Contributors
Full Changelog: oxidecomputer/oxide-tokio-rt@v0.1.3...v0.1.4
Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.