Prevent loop rate tasks from slipping all the time #13758
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andyp1per
force-pushed
the
pr-fast-loop-slip
branch
from
3c2600c
to
dbd0880
Compare
andyp1per
force-pushed
the
pr-fast-loop-slip
branch
2 times, most recently
from
a2154c3
to
fa2a510
Compare
andyp1per
force-pushed
the
pr-fast-loop-slip
branch
from
fa2a510
to
b004875
Compare
Merged
|
This was merged as part of my FFT changes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The AP_Vehicle scheduler table comes after the vehicle specific tables. This means that loop rate tasks will almost always get penalized by slower tasks in the vehicle specific tables especially on slower processors. For FFT this is a problem as we need to reliably increment the gyro sample counters, but in general I believe this is the right thing to do.