From: Leon Hwang <leon.hwang@linux•dev>
To: Yonghong Song <yonghong.song@linux•dev>,
Hui Zhu <hui.zhu@linux•dev>, Alexei Starovoitov <ast@kernel•org>,
Daniel Borkmann <daniel@iogearbox•net>,
John Fastabend <john.fastabend@gmail•com>,
Andrii Nakryiko <andrii@kernel•org>,
Martin KaFai Lau <martin.lau@linux•dev>,
Eduard Zingerman <eddyz87@gmail•com>,
Kumar Kartikeya Dwivedi <memxor@gmail•com>,
Song Liu <song@kernel•org>, Jiri Olsa <jolsa@kernel•org>,
Johannes Weiner <hannes@cmpxchg•org>,
Michal Hocko <mhocko@kernel•org>,
Roman Gushchin <roman.gushchin@linux•dev>,
Shakeel Butt <shakeel.butt@linux•dev>,
Muchun Song <muchun.song@linux•dev>,
JP Kobryn <inwardvessel@gmail•com>,
Andrew Morton <akpm@linux-foundation•org>,
Shuah Khan <shuah@kernel•org>,
davem@davemloft•net, Jakub Kicinski <kuba@kernel•org>,
Jesper Dangaard Brouer <hawk@kernel•org>,
Stanislav Fomichev <sdf@fomichev•me>,
KP Singh <kpsingh@kernel•org>, Tao Chen <chen.dylane@linux•dev>,
Mykyta Yatsenko <yatsenko@meta•com>,
Leon Hwang <leon.hwang@linux•dev>,
Anton Protopopov <a.s.protopopov@gmail•com>,
Amery Hung <ameryhung@gmail•com>,
Tobias Klauser <tklauser@distanz•ch>,
Eyal Birger <eyal.birger@gmail•com>, Rong Tao <rongtao@cestc•cn>,
Hao Luo <haoluo@google•com>,
Peter Zijlstra <peterz@infradead•org>,
Miguel Ojeda <ojeda@kernel•org>,
Nathan Chancellor <nathan@kernel•org>,
Kees Cook <kees@kernel•org>, Tejun Heo <tj@kernel•org>,
Jeff Xu <jeffxu@chromium•org>,
mkoutny@suse•com, Jan Hendrik Farr <kernel@jfarr•cc>,
Christian Brauner <brauner@kernel•org>,
Randy Dunlap <rdunlap@infradead•org>,
Brian Gerst <brgerst@gmail•com>,
Masahiro Yamada <masahiroy@kernel•org>,
Willem de Bruijn <willemb@google•com>,
Jason Xing <kerneljasonxing@gmail•com>,
Paul Chaignon <paul.chaignon@gmail•com>,
Chen Ridong <chenridong@huaweicloud•com>,
Lance Yang <lance.yang@linux•dev>,
Jiayuan Chen <jiayuan.chen@linux•dev>,
linux-kernel@vger•kernel.org, bpf@vger•kernel.org,
cgroups@vger•kernel.org, linux-mm@kvack•org,
netdev@vger•kernel.org, linux-kselftest@vger•kernel.org
Cc: geliang@kernel•org, baohua@kernel•org
Subject: Re: [RFC PATCH bpf-next v7 04/11] libbpf: introduce bpf_map__attach_struct_ops_opts()
Date: Thu, 28 May 2026 13:53:25 +0800 [thread overview]
Message-ID: <ac7a32d5-6c31-41a9-8a36-e64be12f45a3@linux.dev> (raw)
In-Reply-To: <2fd62ec0-c594-4ac2-a95d-29eafbcb74d6@linux.dev>
On 27/5/26 23:43, Yonghong Song wrote:
>
>
> On 5/25/26 7:20 PM, Hui Zhu wrote:
>> From: Roman Gushchin <roman.gushchin@linux•dev>
[...]
>> diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map
>> index dfed8d60af05..6105619b5ecf 100644
>> --- a/tools/lib/bpf/libbpf.map
>> +++ b/tools/lib/bpf/libbpf.map
>> @@ -454,6 +454,7 @@ LIBBPF_1.7.0 {
>> bpf_prog_assoc_struct_ops;
>> bpf_program__assoc_struct_ops;
>> btf__permute;
>> + bpf_map__attach_struct_ops_opts;
>
> Function bpf_map__attach_struct_ops_opts should be in
> LIBBPF_1.8.0.
>
Pls also keep it in alphabet order.
Thanks,
Leon
>> } LIBBPF_1.6.0;
>> LIBBPF_1.8.0 {
>
>
>
next prev parent reply other threads:[~2026-05-28 5:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 2:20 [RFC PATCH bpf-next v7 00/11] mm: BPF struct_ops for dynamic memory protection and async reclaim Hui Zhu
2026-05-26 2:20 ` [RFC PATCH bpf-next v7 01/11] bpf: move bpf_struct_ops_link into bpf.h Hui Zhu
2026-05-26 2:20 ` [RFC PATCH bpf-next v7 02/11] bpf: allow attaching struct_ops to cgroups Hui Zhu
2026-05-26 3:19 ` bot+bpf-ci
2026-05-26 2:20 ` [RFC PATCH bpf-next v7 03/11] libbpf: fix return value on memory allocation failure Hui Zhu
2026-05-26 3:06 ` bot+bpf-ci
2026-05-26 2:20 ` [RFC PATCH bpf-next v7 04/11] libbpf: introduce bpf_map__attach_struct_ops_opts() Hui Zhu
2026-05-26 3:06 ` bot+bpf-ci
2026-05-27 15:43 ` Yonghong Song
2026-05-28 5:53 ` Leon Hwang [this message]
2026-05-26 2:20 ` [RFC PATCH bpf-next v7 05/11] bpf: Pass flags in bpf_link_create for struct_ops Hui Zhu
2026-05-26 2:24 ` [RFC PATCH bpf-next v7 06/11] mm: memcontrol: Add BPF struct_ops for memory controller Hui Zhu
2026-05-26 3:19 ` bot+bpf-ci
2026-05-26 2:24 ` [RFC PATCH bpf-next v7 07/11] mm/bpf: Add bpf_try_to_free_mem_cgroup_pages kfunc Hui Zhu
2026-05-26 3:06 ` bot+bpf-ci
2026-05-26 2:24 ` [RFC PATCH bpf-next v7 08/11] selftests/bpf: Add tests for memcg_bpf_ops Hui Zhu
2026-05-26 2:27 ` [RFC PATCH bpf-next v7 09/11] selftests/bpf: Add test for memcg_bpf_ops hierarchies Hui Zhu
2026-05-26 2:27 ` [RFC PATCH bpf-next v7 10/11] selftests/bpf: Add selftest for memcg async reclaim via BPF Hui Zhu
2026-05-26 3:06 ` bot+bpf-ci
2026-05-26 2:27 ` [RFC PATCH bpf-next v7 11/11] samples/bpf: Add memcg priority control and async reclaim example Hui Zhu
2026-05-26 13:41 ` [RFC PATCH bpf-next v7 00/11] mm: BPF struct_ops for dynamic memory protection and async reclaim Usama Arif
2026-05-27 9:31 ` teawater
2026-05-27 8:47 ` Michal Hocko
2026-05-28 8:27 ` teawater
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=ac7a32d5-6c31-41a9-8a36-e64be12f45a3@linux.dev \
--to=leon.hwang@linux$(echo .)dev \
--cc=a.s.protopopov@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ameryhung@gmail$(echo .)com \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=baohua@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=brauner@kernel$(echo .)org \
--cc=brgerst@gmail$(echo .)com \
--cc=cgroups@vger$(echo .)kernel.org \
--cc=chen.dylane@linux$(echo .)dev \
--cc=chenridong@huaweicloud$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=eddyz87@gmail$(echo .)com \
--cc=eyal.birger@gmail$(echo .)com \
--cc=geliang@kernel$(echo .)org \
--cc=hannes@cmpxchg$(echo .)org \
--cc=haoluo@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=hui.zhu@linux$(echo .)dev \
--cc=inwardvessel@gmail$(echo .)com \
--cc=jeffxu@chromium$(echo .)org \
--cc=jiayuan.chen@linux$(echo .)dev \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kees@kernel$(echo .)org \
--cc=kernel@jfarr$(echo .)cc \
--cc=kerneljasonxing@gmail$(echo .)com \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=lance.yang@linux$(echo .)dev \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=martin.lau@linux$(echo .)dev \
--cc=masahiroy@kernel$(echo .)org \
--cc=memxor@gmail$(echo .)com \
--cc=mhocko@kernel$(echo .)org \
--cc=mkoutny@suse$(echo .)com \
--cc=muchun.song@linux$(echo .)dev \
--cc=nathan@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ojeda@kernel$(echo .)org \
--cc=paul.chaignon@gmail$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=roman.gushchin@linux$(echo .)dev \
--cc=rongtao@cestc$(echo .)cn \
--cc=sdf@fomichev$(echo .)me \
--cc=shakeel.butt@linux$(echo .)dev \
--cc=shuah@kernel$(echo .)org \
--cc=song@kernel$(echo .)org \
--cc=tj@kernel$(echo .)org \
--cc=tklauser@distanz$(echo .)ch \
--cc=willemb@google$(echo .)com \
--cc=yatsenko@meta$(echo .)com \
--cc=yonghong.song@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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