Stream: SIG-Embedded

Topic: 2024 November 26


view this post on Zulip Chris Woods (Nov 26 2024 at 03:45):

Hi Folks, looking forward to seeing those who can make it tomorrow (Tuesday 26th). There was a set of points for discussion which I've rolled over from last time, please do check them out: https://github.com/bytecodealliance/meetings/blob/main/SIG-Embedded/2024/11-26-Meeting-notes.md

Contribute to bytecodealliance/meetings development by creating an account on GitHub.

view this post on Zulip lum1n0us (Nov 26 2024 at 05:19):

I'm curious if there's a place that gathers all our ideas and conversations about shared memory? I've noticed that the information is dispersed through emails, PRs, issues, and meeting minutes, and can't be certain that everyone is on the same page. At the very least, I'm aware that I've missed something, but I'm not sure which part.

view this post on Zulip Ralph (Nov 26 2024 at 14:27):

yeah, that would be totes coolio.....

view this post on Zulip Chris Woods (Nov 27 2024 at 19:43):

Hi Folks, the youtube video of our meeting is now available here : YouTube - - YouTube

view this post on Zulip Chris Woods (Nov 27 2024 at 19:44):

@lum1n0us @Ralph - Indeed coolio, and I seem to be volunteered myself during the SIG to move the email conversation over to a GitHub issue.

Progress will be a little delayed due to the the holidays this week.

view this post on Zulip Ralph (Nov 27 2024 at 20:37):

Gotta have holidays

view this post on Zulip Christof Petig (Nov 29 2024 at 12:20):

I just completed an example of using shared memory in a safe way (at least the documented semantics should make sure that ownership is never violated for the component model) which is still easy to implement (unless you need to drill holes across wasmtime component model helper functions to get the linear memory pointer) and reason about. I would love to hear more about this:

https://github.com/cpetig/wasm-shm-test

As Luke pointed out this conceptually forms a stream of frames, with the option to synchronize reader and writer via blocking or signalling in the host. So after the initial communication of the shm id reader and writer can independently communicate over this channel. [This isn't yet implemented in this PoC]

Prototype for zero-copy shared memory inter-component exchange - cpetig/wasm-shm-test

view this post on Zulip Ralph (Nov 29 2024 at 13:14):

Wow, great work here! I'll dive into this....


Last updated: Dec 23 2024 at 13:07 UTC