wasmtime: pool async stack allocations on unix #3830
Merged
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
coolreader18
requested changes
Dec 5, 2025
Centril
force-pushed
the
centril/wasmtime-pooling-stack-allocator
branch
from
3c24662 to
c5b41ae
Compare
coolreader18
approved these changes
Dec 10, 2025
Centril
force-pushed
the
centril/wasmtime-pooling-stack-allocator
branch
from
1e705d0 to
dd2be6b
Compare
Centril
force-pushed
the
centril/wasmtime-pooling-stack-allocator
branch
from
dd2be6b to
5edaedc
Compare
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
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.
Description of Changes
Uses
with_host_stackto provide aStackCreatorthat poolsFiberStacks.This does not use the pooling instance allocator and is limited to just stacks.
API and ABI breaking changes
None
Expected complexity level and risk
3? Some unsafe and wasmtime internals relied upon.
Testing
Covered by existing tests.