From: Kui-Feng Lee <sinquersw@gmail.com>
To: Martin KaFai Lau <martin.lau@linux.dev>, Kui-Feng Lee <kuifeng@meta.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, song@kernel.org,
kernel-team@meta.com, andrii@kernel.org, sdf@google.com
Subject: Re: [PATCH bpf-next v7 6/8] libbpf: Update a bpf_link with another struct_ops.
Date: Fri, 17 Mar 2023 14:40:10 -0700 [thread overview]
Message-ID: <a4dcfcf6-ac5b-3767-daf7-a055dfcac3cb@gmail.com> (raw)
In-Reply-To: <2cb64258-e566-00c3-7a40-f63e90f3bf97@linux.dev>
On 3/17/23 12:42, Martin KaFai Lau wrote:
> On 3/15/23 7:36 PM, Kui-Feng Lee wrote:
>> Introduce bpf_link__update_map(), which allows to atomically update
>> underlying struct_ops implementation for given struct_ops BPF link
>>
>> Signed-off-by: Kui-Feng Lee <kuifeng@meta.com>
>> ---
>> tools/lib/bpf/libbpf.c | 30 ++++++++++++++++++++++++++++++
>> tools/lib/bpf/libbpf.h | 1 +
>> tools/lib/bpf/libbpf.map | 1 +
>> 3 files changed, 32 insertions(+)
>>
>> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
>> index 6dbae7ffab48..63ec1f8fe8a0 100644
>> --- a/tools/lib/bpf/libbpf.c
>> +++ b/tools/lib/bpf/libbpf.c
>> @@ -11659,6 +11659,36 @@ struct bpf_link
>> *bpf_map__attach_struct_ops(const struct bpf_map *map)
>> return &link->link;
>> }
>> +/*
>> + * Swap the back struct_ops of a link with a new struct_ops map.
>> + */
>> +int bpf_link__update_map(struct bpf_link *link, const struct bpf_map
>> *map)
>> +{
>> + struct bpf_link_struct_ops *st_ops_link;
>> + __u32 zero = 0;
>> + int err, fd;
>> +
>> + if (!bpf_map__is_struct_ops(map) || map->fd < 0)
>> + return -EINVAL;
>> +
>> + st_ops_link = container_of(link, struct bpf_link_struct_ops, link);
>> + /* Ensure the type of a link is correct */
>> + if (st_ops_link->map_fd < 0)
>> + return -EINVAL;
>> +
>> + err = bpf_map_update_elem(map->fd, &zero,
>> map->st_ops->kern_vdata, 0);
>> + if (err && err != -EBUSY)
>> + return err;
>> +
>> + fd = bpf_link_update(link->fd, map->fd, NULL);
>
> bpf_link_update() returns ok/error. Using "fd = ..." is confusing. Use
> "err = ..." instead and remove the need of "int fd;".
got it.
>
>> + if (fd < 0)
>> + return fd;
>> +
>> + st_ops_link->map_fd = map->fd;
>> +
>> + return 0;
>> +}
>> +
>> typedef enum bpf_perf_event_ret (*bpf_perf_event_print_t)(struct
>> perf_event_header *hdr,
>> void *private_data);
>> diff --git a/tools/lib/bpf/libbpf.h b/tools/lib/bpf/libbpf.h
>> index db4992a036f8..1615e55e2e79 100644
>> --- a/tools/lib/bpf/libbpf.h
>> +++ b/tools/lib/bpf/libbpf.h
>> @@ -719,6 +719,7 @@ bpf_program__attach_freplace(const struct
>> bpf_program *prog,
>> struct bpf_map;
>> LIBBPF_API struct bpf_link *bpf_map__attach_struct_ops(const struct
>> bpf_map *map);
>> +LIBBPF_API int bpf_link__update_map(struct bpf_link *link, const
>> struct bpf_map *map);
>> struct bpf_iter_attach_opts {
>> size_t sz; /* size of this struct for forward/backward
>> compatibility */
>> diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map
>> index 50dde1f6521e..cc05be376257 100644
>> --- a/tools/lib/bpf/libbpf.map
>> +++ b/tools/lib/bpf/libbpf.map
>> @@ -387,6 +387,7 @@ LIBBPF_1.2.0 {
>> global:
>> bpf_btf_get_info_by_fd;
>> bpf_link_get_info_by_fd;
>> + bpf_link__update_map;
>> bpf_map_get_info_by_fd;
>> bpf_prog_get_info_by_fd;
>> } LIBBPF_1.1.0;
>
next prev parent reply other threads:[~2023-03-17 21:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 2:36 [PATCH bpf-next v7 0/8] Transit between BPF TCP congestion controls Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 1/8] bpf: Retire the struct_ops map kvalue->refcnt Kui-Feng Lee
2023-03-17 16:47 ` Martin KaFai Lau
2023-03-17 20:41 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 2/8] net: Update an existing TCP congestion control algorithm Kui-Feng Lee
2023-03-17 15:23 ` Daniel Borkmann
2023-03-17 17:18 ` Martin KaFai Lau
2023-03-17 17:23 ` Daniel Borkmann
2023-03-17 21:46 ` Kui-Feng Lee
2023-03-17 23:07 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 3/8] bpf: Create links for BPF struct_ops maps Kui-Feng Lee
2023-03-17 18:10 ` Martin KaFai Lau
2023-03-17 20:52 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 4/8] libbpf: Create a bpf_link in bpf_map__attach_struct_ops() Kui-Feng Lee
2023-03-17 18:44 ` Martin KaFai Lau
2023-03-17 21:00 ` Kui-Feng Lee
2023-03-17 22:23 ` Andrii Nakryiko
2023-03-17 23:48 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 5/8] bpf: Update the struct_ops of a bpf_link Kui-Feng Lee
2023-03-17 19:23 ` Martin KaFai Lau
2023-03-17 21:39 ` Kui-Feng Lee
2023-03-18 1:11 ` Kui-Feng Lee
2023-03-18 5:38 ` Martin KaFai Lau
2023-03-17 22:27 ` Andrii Nakryiko
2023-03-18 0:41 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 6/8] libbpf: Update a bpf_link with another struct_ops Kui-Feng Lee
2023-03-17 19:42 ` Martin KaFai Lau
2023-03-17 21:40 ` Kui-Feng Lee [this message]
2023-03-17 22:33 ` Andrii Nakryiko
2023-03-18 1:17 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 7/8] libbpf: Use .struct_ops.link section to indicate a struct_ops with a link Kui-Feng Lee
2023-03-17 22:35 ` Andrii Nakryiko
2023-03-16 2:36 ` [PATCH bpf-next v7 8/8] selftests/bpf: Test switching TCP Congestion Control algorithms Kui-Feng 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=a4dcfcf6-ac5b-3767-daf7-a055dfcac3cb@gmail.com \
--to=sinquersw@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@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