Skip to content

tcp: make accept and finish-connect async, instead of polling with noop waker - #10003

Closed
pchickey wants to merge 2 commits into
mainfrom
pch/tcp_finish_connect_async
Closed

pchickey wants to merge 2 commits into
mainfrom
pch/tcp_finish_connect_async

Conversation

@pchickey

@pchickey pchickey commented Jan 13, 2025 •

Copy link
Copy Markdown
Contributor

Includes #9691
Fixes #9938

Still WIP - letting CI chew on it

Heap-Hop and others added 2 commits January 13, 2025 15:10
this changes the behavior:
* if a connect is not complete when finish-connect is called, it will
  block from wasm guest while the host code awaits completion.
* no longer use a noop waker to poll the connect future, so that tokio
  doesn't miss the changes
@pchickey
pchickey marked this pull request as ready for review January 13, 2025 23:16
@pchickey
pchickey requested a review from a team as a code owner January 13, 2025 23:16
@pchickey
pchickey requested review from fitzgen and removed request for a team January 13, 2025 23:16
@pchickey pchickey changed the title tcp: make finish-connect async, instead of polling with noop waker tcp: make accept and finish-connect async, instead of polling with noop waker Jan 14, 2025

@fitzgen fitzgen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@github-actions github-actions Bot added the wasi Issues pertaining to WASI label Jan 14, 2025
@pchickey pchickey closed this Jan 14, 2025
@pchickey
pchickey deleted the pch/tcp_finish_connect_async branch January 14, 2025 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasi Issues pertaining to WASI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WASI socket read returns 0 when it should return at least 1

3 participants