map: fix TestMapBatch failing with ENOSPC for hash maps#1485
Merged
lmb merged 1 commit intocilium:mainfrom Jun 11, 2024
Merged
Conversation
The batch lookup API for hash maps returns ENOSPC when a bucket doesn't fit into the provided batch. This is unfortunate since user space has no way to figure out what the largest bucket size is. This makes the API very awkward to use. It also seems that hash tables don't deal well with sequential keys, hashing them into the same bucket with fairly high probability. Fix the flaky test by always making the batch size equal to the map size, which means we can never trigger ENOSPC. Also make the error message more descriptive. Fixes: cilium#1390 Signed-off-by: Lorenz Bauer <[email protected]>
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
1 participant
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 batch lookup API for hash maps returns ENOSPC when a bucket doesn't fit into the provided batch. This is unfortunate since user space has no way to figure out what the largest bucket size is. This makes the API very awkward to use.
It also seems that hash tables don't deal well with sequential keys, hashing them into the same bucket with fairly high probability.
Fix the flaky test by always making the batch size equal to the map size, which means we can never trigger ENOSPC. Also make the error message more descriptive.
Fixes: #1390