On Tue, Jul 9, 2019 at 1:27 PM Edward Cree <ecree@xxxxxxxxxxxxxx> wrote: > > On 05/07/2019 22:15, Daniel Borkmann wrote: > > On 07/05/2019 05:50 PM, Andrii Nakryiko wrote: > >> This patch set implements an update to how BTF-defined maps are specified. The > >> change is in how integer attributes, e.g., type, max_entries, map_flags, are > >> specified: now they are captured as part of map definition struct's BTF type > >> information (using array dimension), eliminating the need for compile-time > >> data initialization and keeping all the metadata in one place. > >> > >> All existing selftests that were using BTF-defined maps are updated, along > >> with some other selftests, that were switched to new syntax. > BTW is this changing the BTF format spec, and if so why isn't it accompanied by > a patch to Documentation/bpf/btf.rst? It looks like that doc still talks about > BPF_ANNOTATE_KV_PAIR, which seems to be long gone. It didn't remove BPF_ANNOTATE_KV_PAIR and you can still use it and libbpf will continue supporting it for the time being. But I'll update the doc with new syntax, thanks for reminding! > > -Ed
