-
Notifications
You must be signed in to change notification settings - Fork 27
notification: Replace async block with poll_recv #510
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.
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
Closed
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
81e83bc
notification: Fix stalled connection due to dropped wakers in poll_next
lexnv a8625fc
Merge branch 'master' into lexnv/poll-wakers-connections
lexnv 412afb0
notif: Change poll order to prioritize sync_rx
lexnv 22eaf39
Merge remote-tracking branch 'origin/lexnv/poll-wakers-connections' i…
lexnv b2f3794
Merge branch 'master' into lexnv/poll-wakers-connections
lexnv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://docs.rs/tokio/1.49.0/tokio/sync/mpsc/struct.Receiver.html#cancel-safety
But this is cancel safe. So, I don't get your argument?
The wake up call should still be registered and the entire future be called when there was an event?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, the receivers should be cancel safe. The issue here is with the
let future = async { }. The context waker is registered by the innerrecvcalls inside the temporary future. The future would later on be dropped iffuture.poll_unpinreturnsPoll::Pending. Then, when thesync_rxgot a new notification, it would wake the waker corresponding to the dropped future, causing the poll_next to stall.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But the waker is for the entire task and not just the future. So, the waker just wakes up the entire task and not some particular future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've dug a bit into tokio to figure this out, indeed I'm mistaken with the "stalled connection" because I assumed
recvworked similarly toreserve(the initial issue we noticed in webrtc):The tokio's bounded Receiver uses a waiting list of "context waker" via a wrapper over Semaphore implementation
I assumed that
sync_rx.recv()would call into the semaphoreacquireor similar to place the context waker into the linked list (obtaining an Acquire)sync_rx.recv()future would get dropped immediately, the waker would be removed on Drop from the linked listHowever, the semaphore is only used for capacity. When we call into recv, the Receiver stores the waker into a separate variable:
So regardless if the temporary
futuregets dropped, we'll still wake the proper waker under the hood. This PR justs turns into a tiny optimization to not create and drop a dedicatedasync block:D