Add "Intro to Async Rust and Tokio’s Architecture" #219
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
Owner
|
Looks good, thanks! Sorry for the review delay. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
After an introduction to Rust and asynchronous programming, the post explores how Rust makes writing asynchronous programs easy, using futures and compiler-generated state machines. It then introduces Tokio, an asynchronous runtime for Rust, and explains task scheduling, managing run queues, and the role of the I/O driver in registering resources. Lastly, it goes over asynchronous interfaces for the Linux operating system and discusses io_uring and how it addresses previous shortcomings.
I am the author.