Conversation
|
Memory usage after merging this PR will be: Memory Reportaction_empty_test_c
action_microstep_test_c
action_overwrite_test_c
action_test_c
deadline_test_c
delayed_conn_test_c
event_payload_pool_test_c
event_queue_test_c
nanopb_test_c
physical_clock_test_c
port_test_c
reaction_queue_test_c
request_shutdown_test_c
startup_test_c
tcp_channel_test_c
timer_test_c
|
|
Benchmark results after merging this PR: Benchmark resultsPerformance:PingPongUc: PingPongC: ReactionLatencyUc: ReactionLatencyC: Memory usage:PingPongUc: PingPongC: ReactionLatencyUc: ReactionLatencyC: |
|
I realized there is a couple of things missing:
|
This PR introduces enclaves into reactor-uc. To do so we must extend the platform API with a notion of threads, because each enclave executes in its own execution context. Currently the threading API is only implemented in POSIX and enclaves can thus still be considered experimental.
Enclaves behave as federates and are coordinated decentrally. This means that we could get STP violations and that we do not support ZDC cycles between enclaves