From: Christy Lee <christylee@fb.com>
To: <andrii@kernel.org>, <acme@kernel.org>
Cc: <christyc.y.lee@gmail.com>, <bpf@vger.kernel.org>,
<kernel-team@fb.com>, <linux-perf-users@vger.kernel.org>,
Christy Lee <christylee@fb.com>
Subject: [PATCH bpf-next 0/5] libbpf 1.0: deprecate bpf_map__def() API
Date: Wed, 5 Jan 2022 15:00:52 -0800 [thread overview]
Message-ID: <20220105230057.853163-1-christylee@fb.com> (raw)
bpf_map__def() is rarely used and non-extensible. bpf_map_def fields
can be accessed with appropriate map getters and setters instead.
Deprecate bpf_map__def() API and replace use cases with getters and setters.
Christy Lee (5):
samples/bpf: stop using bpf_map__def() API
bpftool: stop using bpf_map__def() API
perf: stop using bpf_map__def() API
selftests/bpf: stop using bpf_map__def() API
libbpf: deprecate bpf_map__def() API
samples/bpf/xdp_rxq_info_user.c | 10 ++--
tools/bpf/bpftool/gen.c | 12 ++--
tools/bpf/bpftool/struct_ops.c | 4 +-
tools/lib/bpf/libbpf.h | 3 +-
tools/perf/util/bpf-loader.c | 58 ++++++++-----------
tools/perf/util/bpf_map.c | 28 ++++-----
.../selftests/bpf/prog_tests/flow_dissector.c | 2 +-
.../selftests/bpf/prog_tests/global_data.c | 2 +-
.../bpf/prog_tests/global_data_init.c | 2 +-
.../selftests/bpf/prog_tests/sockmap_listen.c | 12 ++--
.../selftests/bpf/prog_tests/tailcalls.c | 36 ++++++------
11 files changed, 79 insertions(+), 90 deletions(-)
--
2.30.2
next reply other threads:[~2022-01-05 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 23:00 Christy Lee [this message]
2022-01-05 23:00 ` [PATCH bpf-next 1/5] samples/bpf: stop using bpf_map__def() API Christy Lee
2022-01-05 23:00 ` [PATCH bpf-next 2/5] bpftool: " Christy Lee
2022-01-05 23:00 ` [PATCH bpf-next 3/5] perf: " Christy Lee
2022-01-06 0:20 ` Andrii Nakryiko
2022-01-06 20:24 ` Arnaldo Carvalho de Melo
2022-01-05 23:00 ` [PATCH bpf-next 4/5] selftests/bpf: " Christy Lee
2022-01-05 23:00 ` [PATCH bpf-next 5/5] libbpf: deprecate " Christy Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220105230057.853163-1-christylee@fb.com \
--to=christylee@fb.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christyc.y.lee@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-perf-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).