optimal nettop so that we avoid scan the whole /proc #139
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
to achieve this goal, we use local cri interface to get required pod information, such as netns, ip, pids. cri v1 has GetContainerEvents methon that can be used to watch container change events, once container changed, we can call ContainerStatus to get container detail info. Unfortunately there is a bug in containerd: only one caller of GetContainerEvents is supported. So now we have to list containers periodically to get caontiner info.
jzwlqx
force-pushed
the
feature/optimize_netop
branch
from
581cea8 to
d15f927
Compare
BSWANG
requested changes
Jan 9, 2024
Lyt99
requested changes
Jan 10, 2024
Lyt99
approved these changes
Jan 10, 2024
BSWANG
approved these changes
Jan 10, 2024
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.
to achieve this goal, we use local cri interface to get required pod information, such as netns, ip, pids.
cri v1 has GetContainerEvents methon that can be used to watch container change events, once container changed, we can call ContainerStatus to get container detail info. Unfortunately there is a bug in containerd: only one caller of GetContainerEvents is supported. So now we have to list containers periodically to get caontiner info.
cri interface return only root pid for every container, so we read cgroup tasks to get all pids of pods.