[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171005144158.14860-1-kraigatgoog@gmail.com>
Date: Thu, 5 Oct 2017 10:41:56 -0400
From: Craig Gallek <kraigatgoog@...il.com>
To: Alexei Starovoitov <ast@...com>,
Daniel Borkmann <daniel@...earbox.net>,
Jesper Dangaard Brouer <brouer@...hat.com>,
"David S . Miller" <davem@...emloft.net>
Cc: Chonggang Li <chonggangli@...gle.com>, netdev@...r.kernel.org
Subject: [PATCH net-next v3 0/2] libbpf: support more map options
From: Craig Gallek <kraig@...gle.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(-)
--
v3:
- explicit memcpy instead of struct assignment.
- remove unnecessary bpf_object__validate_maps function
v2
- determine bpf_map_def structure size dynamically from object file
2.14.2.920.gcf0c67979c-goog
Powered by blists - more mailing lists