-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distribute the start tag within the federation #81
Conversation
… used to distribute start tags
Memory usage after merging this PR will be: Memory Reportaction_microstep_test_c
action_test_c
delayed_conn_test_c
event_queue_test_c
physical_action_test_c
port_test_c
reaction_queue_test_c
shutdown_test_c
startup_test_c
timer_test_c
trigger_data_queue_test_c
|
Memory usage after merging this PR will be: Memory Reportaction_microstep_test_c
action_test_c
delayed_conn_test_c
event_payload_pool_test_c
event_queue_test_c
nanopb_test_c
physical_action_test_c
port_test_c
reaction_queue_test_c
request_shutdown_test_c
shutdown_test_c
startup_test_c
timer_test_c
|
Memory usage after merging this PR will be: Memory Reportaction_microstep_test_c
action_test_c
delayed_conn_test_c
event_payload_pool_test_c
event_queue_test_c
nanopb_test_c
physical_action_test_c
port_test_c
reaction_queue_test_c
request_shutdown_test_c
shutdown_test_c
startup_test_c
timer_test_c
|
Memory usage after merging this PR will be: Memory Reportaction_microstep_test_c
action_test_c
delayed_conn_test_c
event_payload_pool_test_c
event_queue_test_c
nanopb_test_c
physical_action_test_c
port_test_c
reaction_queue_test_c
request_shutdown_test_c
shutdown_test_c
startup_test_c
timer_test_c
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it looks OK. @LasseRosenow and @tanneberger, would you please take a look? Summarized the changes are:
- Federates are now either leader or not, this defines how the start_tag is obtained.
- I add another level of hierarchy in the messages. I call it FederateMessage which contains TaggedMessage and StartTagSignal currently
- We must now defer scheduling timers and startups until we have acquired the start tag.
- Some pico fixes
Memory usage after merging this PR will be: Memory Reportaction_microstep_test_c
action_test_c
delayed_conn_test_c
event_payload_pool_test_c
event_queue_test_c
nanopb_test_c
physical_action_test_c
port_test_c
reaction_queue_test_c
request_shutdown_test_c
shutdown_test_c
startup_test_c
tcp_channel_test_c
timer_test_c
|
This PR addresses #79 with following changes:
leader
and only it will send out start tags to others. This will of course not work if several federates think they are the leader