Wasmtime GitHub notifications bot (Sep 23 2022 at 17:33): Wasmtime GitHub notifications bot (Sep 23 2022 at 17:33):abrown opened PR #4949 from wasi-parallel-cpu to main:
This change implements [
wasi-parallel] in Wasmtime. It addresses only the CPU parallelism (not GPU), since this would introduce additional complexity to an already difficult review (if you're interested about the GPU progress, talk to @egalli). Each commit implements a separate piece to the puzzle. Though most of the changed lines are not the core implementation (seetests,LICENSE, etc.), due to the size of the PR, it may be convenient to look at this commit by commit.[
wasi-parallel]: https://github.com/WebAssembly/wasi-parallelI see several issues highlighted by this change:
- __lacking toolchain support__: in the absence of any other feasible path, the WebAssembly bytes of the kernel code to be executed in parallel are embedded in the host WebAssembly module itself. This is problematic for many reasons, not least of which is the ability for the host WebAssembly module to tamper with the kernel (on the flip side: an intra-module JIT compiler feature!). But that is not the end of it: toolchain support is also lacking simply to produce modules that use atomics and shared memory. For C programs: https://github.com/WebAssembly/wasi-libc/issues/326. For Rust programs: https://github.com/rust-lang/rust/issues/102157. Due to all this, most tests and examples in this crate are meticulously hand-crafted WAT files — once toolchain support improves these difficult-to-maintain files should be replaced.
- __uncomfortable Wasmtime/Wiggle APIs__: this implementation of
wasi-parallelworks by creating new instances of the kernel in each thread of a thread pool — the host module exports a shared memory and the kernel imports it. Getting access to the shared memory from within awasi-parallelinvocation is difficult with Wasmtime/Wiggle: the best way I could think to resolve this is to teach Wiggle toskipa WITX function and then manually implementadd_to_linkerfor that function. This is tedious and error-prone, so I would be excited to discuss better solutions. Note that an almost identical version of this problem will arise when I try to implement [wasi-threads].[
wasi-threads]: https://github.com/WebAssembly/wasi-threadsWhy now? The rationale behind merging this code behind the
wasi-parallelfeature flag is to enable users to try this out locally and to iterate on this in-tree (e.g., toolchain, GPU parts).
Last updated: Oct 23 2024 at 20:03 UTC