datapath/loader: Add map count to verifier complexity records#44652
Merged
datapath/loader: Add map count to verifier complexity records#44652
Conversation
We use a lot of maps in Cilium. The kernel limits us to a max of 64 maps per program. We would like to track how many maps are used by our programs, and how close we are to that limit. So for every permutation of our program we load during the complexity tests, we also query the kernel for the number of maps used by that program, and we add that to the complexity records. Also updated the complexity diff tool to include map count in its output so its both in the JSON files as well as the human readable output. Fixes: #44651 Signed-off-by: Dylan Reimerink <dylan.reimerink@isovalent.com>
Member
Author
|
/ci-verifier |
Member
Author
|
/test |
ti-mo
approved these changes
Mar 11, 2026
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
3 participants
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.
We use a lot of maps in Cilium. The kernel limits us to a max of 64 maps per program. We would like to track how many maps are used by our programs, and how close we are to that limit.
So for every permutation of our program we load during the complexity tests, we also query the kernel for the number of maps used by that program, and we add that to the complexity records.
Also updated the complexity diff tool to include map count in its output so its both in the JSON files as well as the human readable output.
Fixes: #44651