Refactor: Cache pipeline TX frame period at create - #1689
Draft
awilczyns wants to merge 1 commit into
Draft
Conversation
The three tx_st*p_if_frame_late() callbacks derived their DROP_WHEN_LATE grace window per frame as NS_PER_S / st_frame_rate(ops.fps): a float division and a table search in a transport callback, and a divide by zero for an fps outside the timing table (Coverity CID 558964). That zero is unreachable today — the session layer rejects an unknown fps at attach — so this is hardening, not a defect fix. New st_frame_period_ns() derives the period from the exact rational rate; its truncated result is bit-identical to the float form for all 11 timing-table entries. Signed-off-by: Wilczynski, Andrzej <andrzej.wilczynski@intel.com>
This file contains hidden or 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
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 three tx_st*p_if_frame_late() callbacks derived their DROP_WHEN_LATE grace window per frame as NS_PER_S / st_frame_rate(ops.fps): a float division and a table search in a transport callback, and a divide by zero for an fps outside the timing table (Coverity CID 558964). That zero is unreachable today — the session layer rejects an unknown fps at attach — so this is hardening, not a defect fix. New st_frame_period_ns() derives the period from the exact rational rate; its truncated result is bit-identical to the float form for all 11 timing-table entries.