Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow BPFMap.Update() to take arbitrary types as keys/values #31

Closed
grantseltzer opened this issue Jul 6, 2021 · 0 comments · Fixed by #32
Closed

Allow BPFMap.Update() to take arbitrary types as keys/values #31

grantseltzer opened this issue Jul 6, 2021 · 0 comments · Fixed by #32

Comments

@grantseltzer
Copy link
Contributor

Since keys/values can be arbitrary types in bpf code, libbpfgo should also support this. Currently GetUnsafePointer() will fail if what's passed isn't a uint/int/byte slice.

We should be able to just use an unsafe.Pointer, however special care should be taken for testing with arrays, slices, maps, interfaces, deep pointers, etc...
@grantseltzer grantseltzer linked a pull request Jul 9, 2021 that will close this issue
Change BPFMap method Update to unsafe.Pointer #32
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Change BPFMap method Update to unsafe.Pointer
1 participant
@grantseltzer