fix: agent - eBPF Correct the maximum data push delay #8694
+14
−12
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
yinjiping
force-pushed
the
PUSH_DELAY_EXCEEDED
branch
from
5cb9d86 to
bc878ee
Compare
When a delay occurs in the eBPF data push cycle (i.e., the time difference between the current and previous trigger exceeds 100 milliseconds), we set the maximum data push delay to a special value (`PUSH_DELAY_EXCEEDED_MARKER`: 199000) to indicate that a delay has occurred, instead of providing the specific delay value. The reason is that in a multi-core environment, direct variable assignment in eBPF cannot ensure atomicity. Therefore, we use a special value to signify the occurrence of a delay.
yinjiping
force-pushed
the
PUSH_DELAY_EXCEEDED
branch
from
bc878ee to
85362c7
Compare
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.
When a delay occurs in the eBPF data push cycle (i.e., the time difference between the current and previous trigger exceeds 100 milliseconds), we set the maximum data push delay to a special value (
PUSH_DELAY_EXCEEDED_MARKER: 199000) to indicate that a delay has occurred, instead of providing the specific delay value. The reason is that in a multi-core environment, direct variable assignment in eBPF cannot ensure atomicity. Therefore, we use a special value to signify the occurrence of a delay.This PR is for:
Affected branches