forked from microsoft/ebpf-for-windows
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add ebpf_get_next_pinned_object_path (microsoft#4164)
* Add ebpf_get_next_pinned_object_path It's currently not possible to find pinned maps and links. Add a function ebpf_get_next_pinned_object_path which allows doing just that. The paths are returned in lexicographical order, which allows user space to performa a prefix match on the paths. Behind the scenes this is implemented using a linear scan of the hash table, which has quadratic running time. The same is already the case for finding the next object ID, so going with the more desirable semantics makes sense. The existing ebpf_get_next_pinned_program_path() is deprecated because it is less flexible than the new function. Updates microsoft#4161 * Document return value of ebpf_get_next_pinned_object_path Co-authored-by: Dave Thaler <dthaler1968@gmail.com> * Fix possible underflow in get_next_pinned_program_path / object_path * Fix typo in ebpf_pinning_table_get_next_path documentation Co-authored-by: Dave Thaler <dthaler1968@gmail.com> --------- Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
- Loading branch information
Showing
10 changed files
with
285 additions
and
46 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.