Closed MarcinMiklas closed 3 years ago
Sometime ago spin wait was made separate from fixed_timestamp, this caused regression in builds using IGB_LAUNCHTIME_ENABLED=1.
This PR adds launchtime flag to talker which will be set automatically if IGB/ATL_LAUNCHTIME_ENABLED is used.
Otherwise we would need to use spin_wait flag to make launchtime work which would be counter-intuitive.
Both spin_wait and launchtime mode work on WALLCLOCK, but launchtime doesn't need any waiting because it will be done in ethernet driver.
So, we will have 3 modes for packet scheduling:
This looks great! Any other comments?
I approve.
Sometime ago spin wait was made separate from fixed_timestamp, this caused regression in builds using IGB_LAUNCHTIME_ENABLED=1.
This PR adds launchtime flag to talker which will be set automatically if IGB/ATL_LAUNCHTIME_ENABLED is used.
Otherwise we would need to use spin_wait flag to make launchtime work which would be counter-intuitive.
Both spin_wait and launchtime mode work on WALLCLOCK, but launchtime doesn't need any waiting because it will be done in ethernet driver.
So, we will have 3 modes for packet scheduling: