Split BPFMap API into managed and unmanaged
geyslan opened this issue · comments
Currently, we only have one BPFMap API for libbpf-managed and user-created objects (CreateMap). That is a bug since, for the latter case, the BPFMap object is being used without a libbpf map reference.
After #343 (comment), it was decided to split this API (creating a BPFMap type - libbpf unmanaged) as the first step towards implementing the map of maps.
This chore must be also the first step towards refactoring (splitting bpf module, programs, maps into own files) the library - #355.