[erlang-questions] Hard Real Time Erlang

[Tony Rogvall]

On 17 jul 2013, at 19:56, Peer Stritzinger <peerst@REDACTED> wrote:

> 
> On 2013-07-16 08:04:23 +0000, Arie van Wingerden said:
> 
> I have read this article http://www.erlang.se/workshop/2007/proceedings/05nicosi.pdf and I am wondering if there has been any progress in this field.
> 
> Not that I heard of.
> 
> I work around this problem by porting Erlang to RTEMS which is a hard realtime OS.
> So one can do all hard realtime stuff in C, C++ or fwiw even Ada and run it at a higher prio than the Erlang VM
> 
> For more info: http://www.grisp.org
> 
> Even more info will be up soon, also with adding RSS to the site to make tracking it easier.
> 
> I could imagine some subset of Erlang along FRP lines being compiled specially being able to also write hard realtime tasks without C but thats just pipedreams at the moment.

Static Erlang ? I like it :-)

> 
> But often the hard realtime stuff in systems is quite small so keeping just the hard realtime stuff in C and do as much as possible in Erlang on a Grisp system is very feasible.
> 
+1.
Even when I write interrupt handlers in C the code fragments tend to be very tiny, like 10-50 linux code. 
Mostly they update some registers, increment a counter, put some data into a queue for later processing.

Just think about the amount of cpu required to switch to the Erlang VM and dispatch some Erlang code in an interrupt
handler. Holy cow :-)

/Tony

> Cheers,
> -- Peer
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130718/b07e1f3b/attachment.htm>