Stream: general

Topic: Starting new instances of a module as a host function

Fedor Smirnov (Jan 28 2024 at 17:47):

Hi :)

I am exploring how a module could make use of threads on the host side and was thinking of the following scenario:

• the host offers a function to the module which the module can execute
• when the module calls the function, the host
  • creates a new instance of the calling module (the new instance and the "main" module calling the host functions should be in the same store and share memory)
  • starts a new thread
  • within that thread, calls a predefined function of the new module instance

Is something like this possible in general?

I have been trying to implement something into this direction, but could not quite get it to work so far. I have so far been defining host functions via linker.func_wrap(...) and accessing anything I needed via the Caller available within the host function and have difficulties figuring out how I would configure the linker and start up the different module instances.

If this the above scenario is doable, could you please give me some advice of how I would configure the linker for this and how the host function would look?

Thanks a lot! :)

Alex Crichton (Jan 28 2024 at 18:07):

I think you're more-or-less describing the current state of the wasi-threads proposal (it's very experimental), and the implementation in Wasmtime might be of interest to you as it's doing what you're describing I believe

Fedor Smirnov (Jan 28 2024 at 19:08):

Thank you for the pointer :)

If I am reading the code correctly, we create a new Store instance for every new module that we create on a call to the host function we define. So the instances can share memory, in spite of not being in the same store?

And, for the modules to share memory, it is sufficient to add the memory to the linker (line 140)? And then all modules which we instantiate via the host function will have access to it? Is it because they are created from the same instance_pre ?

Alex Crichton (Jan 29 2024 at 15:48):

Sort of but not quite. It's correct that multiple stores are used, one per thread, and that memory is shared. The detail though is that the memory is a SharedMemory and therefore safe to transfer across threads and additionally independent from a store. This is a form of shared memory multithreading for the wasm module itself, which may or may not be what you're looking for. Shared memory multithreading in wasm requires a fair bit of cooperation with the module in question.

Fedor Smirnov (Jan 29 2024 at 18:01):

I see. Will try to implement it following the example you linked to and will see how it goes. Thank you! This has been a great help :)

Last updated: Nov 22 2024 at 16:03 UTC