| Message ID | 20171005144158.14860-1-kraigatgoog@gmail.com |
|---|---|
| Headers | show |
| Series | libbpf: support more map options | expand |
On 10/5/17 7:41 AM, Craig Gallek wrote: > From: Craig Gallek <kraig@google.com> > > The functional change to this series is the ability to use flags when > creating maps from object files loaded by libbpf. In order to do this, > the first patch updates the library to handle map definitions that > differ in size from libbpf's struct bpf_map_def. > > For object files with a larger map definition, libbpf will continue to load > if the unknown fields are all zero, otherwise the map is rejected. If the > map definition in the object file is smaller than expected, libbpf will use > zero as a default value in the missing fields. > > Craig Gallek (2): > libbpf: parse maps sections of varying size > libbpf: use map_flags when creating maps > > tools/lib/bpf/libbpf.c | 72 +++++++++++++++++++++++++++++--------------------- > tools/lib/bpf/libbpf.h | 1 + > 2 files changed, 43 insertions(+), 30 deletions(-) lgtm Acked-by: Alexei Starovoitov <ast@kernel.org>
From: Craig Gallek <kraigatgoog@gmail.com> Date: Thu, 5 Oct 2017 10:41:56 -0400 > The functional change to this series is the ability to use flags when > creating maps from object files loaded by libbpf. In order to do this, > the first patch updates the library to handle map definitions that > differ in size from libbpf's struct bpf_map_def. > > For object files with a larger map definition, libbpf will continue to load > if the unknown fields are all zero, otherwise the map is rejected. If the > map definition in the object file is smaller than expected, libbpf will use > zero as a default value in the missing fields. Series applied, thanks.
From: Craig Gallek <kraig@google.com> The functional change to this series is the ability to use flags when creating maps from object files loaded by libbpf. In order to do this, the first patch updates the library to handle map definitions that differ in size from libbpf's struct bpf_map_def. For object files with a larger map definition, libbpf will continue to load if the unknown fields are all zero, otherwise the map is rejected. If the map definition in the object file is smaller than expected, libbpf will use zero as a default value in the missing fields. Craig Gallek (2): libbpf: parse maps sections of varying size libbpf: use map_flags when creating maps tools/lib/bpf/libbpf.c | 72 +++++++++++++++++++++++++++++--------------------- tools/lib/bpf/libbpf.h | 1 + 2 files changed, 43 insertions(+), 30 deletions(-)