Skip to content
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

Set thread information earlier in exec_env creation #3967

Merged
merged 1 commit into from
Dec 23, 2024

Conversation

sjamesr
Copy link
Contributor

@sjamesr sjamesr commented Dec 19, 2024

No description provided.

@sjamesr
Copy link
Contributor Author

sjamesr commented Dec 19, 2024

This tries to address #3966.

For boundary checking, WAMR calls `pthread_attr_np`, which is
unfortunately quite slow on Linux when not called on the main thread
(see bytecodealliance#3966
for discussion).

This change moves the cost of stack bounds checking earlier in the
wasm_exec_env creation process. The idea is that it's perhaps better to
pay the price when creating the execution environment rather than in the
first function call.

The original code is left in place inside
`call_wasm_with_hw_bound_check` in case the `wasm_exec_env` is created
via `wasm_runtime_spawn_exec_env`.
@sjamesr sjamesr force-pushed the set_thread_info_earlier branch from 2f5ec3d to e39e97d Compare December 20, 2024 17:39
Copy link
Collaborator

@xujuntwt95329 xujuntwt95329 left a comment

Choose a reason for hiding this comment

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

LGTM

@lum1n0us lum1n0us merged commit 8ac0649 into bytecodealliance:main Dec 23, 2024
383 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants