From: Yonghong Song <yonghong.song@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [RFC PATCH bpf-next 3/5] libbpf: Add link support for BPF_PROG_TYPE_SK_MSG
Date: Sat, 9 Mar 2024 10:49:14 -0800 [thread overview]
Message-ID: <dff48e21-8603-427f-a05d-b9bd5775ce09@linux.dev> (raw)
In-Reply-To: <CAEf4Bzb1TpvMU8V9PrO9j35H=z4j4bqvdVGE2JfF4gGzVnGGPA@mail.gmail.com>
On 3/8/24 5:01 PM, Andrii Nakryiko wrote:
> On Tue, Mar 5, 2024 at 12:22 PM Yonghong Song <yonghong.song@linux.dev> wrote:
>> Introduce a libbpf API bpf_program__attach_sk_msg() which allows
>> user to get a bpf_link. The API makes auto-deletion easier and
>> also allows user space application easier as link based APIs
>> are used for all programs.
>>
>> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
>> ---
>> tools/lib/bpf/libbpf.c | 8 ++++++++
>> tools/lib/bpf/libbpf.h | 3 +++
>> tools/lib/bpf/libbpf.map | 1 +
>> 3 files changed, 12 insertions(+)
>>
>> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
>> index 97b573516675..b3982bb3f979 100644
>> --- a/tools/lib/bpf/libbpf.c
>> +++ b/tools/lib/bpf/libbpf.c
>> @@ -149,6 +149,7 @@ static const char * const link_type_name[] = {
>> [BPF_LINK_TYPE_TCX] = "tcx",
>> [BPF_LINK_TYPE_UPROBE_MULTI] = "uprobe_multi",
>> [BPF_LINK_TYPE_NETKIT] = "netkit",
>> + [BPF_LINK_TYPE_SK_MSG] = "sk_msg",
>> };
>>
>> static const char * const map_type_name[] = {
>> @@ -12280,6 +12281,13 @@ bpf_program__attach_netkit(const struct bpf_program *prog, int ifindex,
>> return bpf_program_attach_fd(prog, ifindex, "netkit", &link_create_opts);
>> }
>>
>> +struct bpf_link *
>> +bpf_program__attach_sk_msg(const struct bpf_program *prog, int map_fd,
>> + enum bpf_attach_type attach_type)
> Why do we need to allow users to override attach_type? Why can't it
> come from bpf_program's expected attach type?
The interface is similar to previously used bpf_prog_attach(), but you are
right that this may not be needed. Let me double check.
>
>> +{
>> + return __bpf_program_attach_fd(prog, map_fd, attach_type, "sk_msg", NULL);
>> +}
>> +
>> struct bpf_link *bpf_program__attach_freplace(const struct bpf_program *prog,
>> int target_fd,
>> const char *attach_func_name)
>> diff --git a/tools/lib/bpf/libbpf.h b/tools/lib/bpf/libbpf.h
>> index 5723cbbfcc41..c8448f05e8d6 100644
>> --- a/tools/lib/bpf/libbpf.h
>> +++ b/tools/lib/bpf/libbpf.h
>> @@ -786,6 +786,9 @@ bpf_program__attach_netns(const struct bpf_program *prog, int netns_fd);
>> LIBBPF_API struct bpf_link *
>> bpf_program__attach_xdp(const struct bpf_program *prog, int ifindex);
>> LIBBPF_API struct bpf_link *
>> +bpf_program__attach_sk_msg(const struct bpf_program *prog, int map_fd,
>> + enum bpf_attach_type attach_type);
>> +LIBBPF_API struct bpf_link *
>> bpf_program__attach_freplace(const struct bpf_program *prog,
>> int target_fd, const char *attach_func_name);
>>
>> diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map
>> index 86804fd90dd1..c59986c6dbc5 100644
>> --- a/tools/lib/bpf/libbpf.map
>> +++ b/tools/lib/bpf/libbpf.map
>> @@ -410,6 +410,7 @@ LIBBPF_1.3.0 {
>>
>> LIBBPF_1.4.0 {
>> global:
>> + bpf_program__attach_sk_msg;
>> bpf_token_create;
>> btf__new_split;
>> btf_ext__raw_data;
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2024-03-09 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 20:21 [RFC PATCH bpf-next 0/5] Add bpf_link support for sk_msg prog Yonghong Song
2024-03-05 20:22 ` [RFC PATCH bpf-next 1/5] bpf: Add link " Yonghong Song
2024-03-09 0:59 ` Andrii Nakryiko
2024-03-09 18:41 ` Yonghong Song
2024-03-10 19:23 ` Jakub Sitnicki
2024-03-11 21:58 ` Yonghong Song
2024-03-11 8:30 ` Jiri Olsa
2024-03-11 22:07 ` Yonghong Song
2024-03-05 20:22 ` [RFC PATCH bpf-next 2/5] libbpf: Refactor bpf_program_attach_fd() Yonghong Song
2024-03-09 1:02 ` Andrii Nakryiko
2024-03-09 18:43 ` Yonghong Song
2024-03-05 20:22 ` [RFC PATCH bpf-next 3/5] libbpf: Add link support for BPF_PROG_TYPE_SK_MSG Yonghong Song
2024-03-09 1:01 ` Andrii Nakryiko
2024-03-09 18:49 ` Yonghong Song [this message]
2024-03-05 20:22 ` [RFC PATCH bpf-next 4/5] bpftool: Add link dump support for BPF_LINK_TYPE_SK_MSG Yonghong Song
2024-03-08 16:07 ` Jakub Sitnicki
2024-03-11 21:54 ` Yonghong Song
2024-03-05 20:22 ` [RFC PATCH bpf-next 5/5] selftests/bpf: Add some tests with new bpf_program__attach_sk_msg() API Yonghong Song
2024-03-06 19:19 ` [RFC PATCH bpf-next 0/5] Add bpf_link support for sk_msg prog John Fastabend
2024-03-07 22:47 ` Yonghong Song
2024-03-07 13:01 ` Jakub Sitnicki
2024-03-11 21:53 ` Yonghong Song
2024-03-10 19:52 ` Jakub Sitnicki
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=dff48e21-8603-427f-a05d-b9bd5775ce09@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@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