mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2025-07-10 22:43:15 +00:00
8a55a1e7a1
Propose two enhancements: - Shared heap created from preallocated memory buffer: The user can create a shared heap from a pre-allocated buffer and see that memory region as one large chunk; there's no need to dynamically manage it(malloc/free). The user needs to make sure the native address and size of that memory region are valid. - Introduce shared heap chain: The user can create a shared heap chain, from the wasm app point of view, it's still a continuous memory region in wasm app's point of view while in the native it can consist of multiple shared heaps (each of which is a continuous memory region). For example, one 500MB shared heap 1 and one 500 MB shared heap 2 form a chain, in Wasm's point of view, it's one 1GB shared heap. After these enhancements, the data sharing between wasm apps, and between hosts can be more efficient and flexible. Admittedly shared heap management can be more complex for users, but it's similar to the zero-overhead principle. No overhead will be imposed for the users who don't use the shared heap enhancement or don't use the shared heap at all. |
||
|---|---|---|
| .. | ||
| aot | ||
| aot-stack-frame | ||
| common | ||
| compilation | ||
| custom-section | ||
| gc | ||
| interpreter | ||
| libc-builtin | ||
| linear-memory-aot | ||
| linear-memory-wasm | ||
| linux-perf | ||
| memory64 | ||
| running-modes | ||
| runtime-common | ||
| shared-heap | ||
| shared-utils | ||
| tid-allocator | ||
| wasm-c-api | ||
| wasm-vm | ||
| CMakeLists.txt | ||
| unit_common.cmake | ||