[riot-devel] remote forking and scheduling
Raphael.Hiesgen at haw-hamburg.de
Wed Jun 1 18:06:33 CEST 2016
forking a process for this purpose hasn’t been on my mind yet. Do you actually need to transfer processes or is the goal to offload work depending on collected input data or … what is the advantage of forking over, let’s say, message passing? You could run a process on a backend server that accepts messages, performs your calculations.
I do mention message passing because we are working to port the C++ Actor Framework (CAF)  to RIOT. Actors are lightweight entities that communicate via messages and are scheduled in a thread pool. We already got the core library working (although a lot has changed since), but the network layer still needs a lot of work to be suitable for IoT scenarios.
Would this fit your use-case? Are you looking for things like distributed scheduling or (pointing to a comment from one of your earlier emails) do you imagine the offloading process to be more automated and without the need for developers to implement the backend themselves?
> On Jun 1, 2016, at 1:02 PM, Arash Shafiei <arash at u.nus.edu> wrote:
> Has anyone worked on or thought about remote forking in the context of Internet of Things?
> The idea is to have a fork which creates a process on another machine of the same network. Then, there would be also a scheduler to schedule those remote processes.
> Is there anything there related to a distributed forking and scheduling of processes and threads?
> Would such thing be useful for IoT applications?
> devel mailing list
> devel at riot-os.org
More information about the devel