4 ms·
quick-question: why go the `rtems` route ? would 'isolcpus' not work in this case ? -- thanks !
by signa11 1y ago
quick-question: why go the `rtems` route ? would 'isolcpus' not work in this case ?
--
thanks !
- plainOldText 1y agoI am not associated with the project, so I cannot answer that.
- peerst 1y agoWith Linux we can only run on larger embedded CPUs that support virtual memory well enough. With RTEMS we can go towards much smaller platforms.
- peerst 1y agoAddendum: we have Buildroot and Yocto based platforms too. Not clear on the website right now but we have three platforms actually: * GRiSP Metal - aka just GRiSP (Erlang/Elxiir + RTEMS) * GRiSP Alloy - Buildroot Linux based, starts the Erlang/Elixir runtime as process 1 similar to Nerves but more language agnostic (Nerves is for Elixir only) and we support RT Linux and running multiple Erlang Runtimes at different priorities * GRiSP Forge - Similar to alloy but Yocto based. The idea is that from the high level language level they are more or less interchangeable.
- signa11 1y agoah ! indeed it can. do such platforms have 18m of memory and then some ?