On Tue, Aug 4, 2020 at 10:51 PM Yonghong Song <yhs@xxxxxx> wrote: > > Andrii raised a concern that current uapi for bpf iterator map > element is a little restrictive and not suitable for future potential > complex customization. This is a valid suggestion, considering people > may indeed add more complex custimization to the iterator, e.g., > cgroup_id + user_id, etc. for task or task_file. Another example might > be map_id plus additional control so that the bpf iterator may bail > out a bucket earlier if a bucket has too many elements which may hold > lock too long and impact other parts of systems. > > Patch #1 modified uapi with kernel changes. Patch #2 > adjusted libbpf api accordingly. > > Changelogs: > v3 -> v4: > . add a forward declaration of bpf_iter_link_info in > tools/lib/bpf/bpf.h in case that libbpf is built against > not-latest uapi bpf.h. > . target the patch set to "bpf" instead of "bpf-next" Applied. Thanks
