From: Yonghong Song <yhs@meta.com>
To: Yosry Ahmed <yosryahmed@google.com>,
Martin KaFai Lau <martin.lau@linux.dev>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Yonghong Song <yhs@fb.com>, bpf <bpf@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>, KP Singh <kpsingh@kernel.org>,
Martin KaFai Lau <martin.lau@kernel.org>,
Tejun Heo <tj@kernel.org>, Stanislav Fomichev <sdf@google.com>
Subject: Re: [PATCH bpf-next 2/5] bpf: Implement cgroup storage available to non-cgroup-attached bpf progs
Date: Tue, 18 Oct 2022 11:26:20 -0700 [thread overview]
Message-ID: <da3d44e2-4d3e-89f7-35f0-849f6f603f05@meta.com> (raw)
In-Reply-To: <CAJD7tkY5DZK9uO=rnNWTFoHU3qnbsj74engcC8VYyzQaJm1PFA@mail.gmail.com>
On 10/18/22 11:11 AM, Yosry Ahmed wrote:
> On Tue, Oct 18, 2022 at 11:08 AM Martin KaFai Lau <martin.lau@linux.dev> wrote:
>>
>> On 10/18/22 10:17 AM, Alexei Starovoitov wrote:
>>> On Tue, Oct 18, 2022 at 10:08 AM <sdf@google.com> wrote:
>>>>>>
>>>>>> '#define BPF_MAP_TYPE_CGROUP_STORAGE BPF_MAP_TYPE_CGRP_LOCAL_STORAGE /*
>>>>>> depreciated by BPF_MAP_TYPE_CGRP_STORAGE */' in the uapi.
>>>>>>
>>>>>> The new cgroup storage uses a shorter name "cgrp", like
>>>>>> BPF_MAP_TYPE_CGRP_STORAGE and bpf_cgrp_storage_get()?
>>>>
>>>>> This might work and the naming convention will be similar to
>>>>> existing sk/inode/task storage.
>>>>
>>>> +1, CGRP_STORAGE sounds good!
>>>
>>> +1 from me as well.
>>>
>>> Something like this ?
>>> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
>>> index 17f61338f8f8..13dcb2418847 100644
>>> --- a/include/uapi/linux/bpf.h
>>> +++ b/include/uapi/linux/bpf.h
>>> @@ -922,7 +922,8 @@ enum bpf_map_type {
>>> BPF_MAP_TYPE_CPUMAP,
>>> BPF_MAP_TYPE_XSKMAP,
>>> BPF_MAP_TYPE_SOCKHASH,
>>> - BPF_MAP_TYPE_CGROUP_STORAGE,
>>> + BPF_MAP_TYPE_CGROUP_STORAGE_DEPRECATED,
>>> + BPF_MAP_TYPE_CGROUP_STORAGE = BPF_MAP_TYPE_CGROUP_STORAGE_DEPRECATED,
>>
>> +1
>>
>>> BPF_MAP_TYPE_REUSEPORT_SOCKARRAY,
>>> BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE,
>>> BPF_MAP_TYPE_QUEUE,
>>> @@ -935,6 +936,7 @@ enum bpf_map_type {
>>> BPF_MAP_TYPE_TASK_STORAGE,
>>> BPF_MAP_TYPE_BLOOM_FILTER,
>>> BPF_MAP_TYPE_USER_RINGBUF,
>>> + BPF_MAP_TYPE_CGRP_STORAGE,
>>> };
Sounds good to me. Will do this in the next revision.
>>>
>>> What are we going to do with BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE ?
>>> Probably should come up with a replacement as well?
>>
>> Yeah, need to come up with a percpu answer for it. The percpu usage has never
>> come up on the sk storage and also the later task/inode storage. or the user is
>> just getting by with an array like map's value.
>>
>> May be the bpf prog can call bpf_mem_alloc() to alloc the percpu memory in the
>> future and then store it as the kptr in the BPF_MAP_TYPE_CGRP_STORAGE?
>
> A percpu cgroup storage would be very beneficial for cgroup statistics
> collection, things like the selftest in
> tools/testing/selftests/bpf/progs/cgroup_hierarchical_stats.c
> currently uses a percpu hashmap indexed by cgroup id, so using a
> percpu cgroup storage instead would be a nice upgrade.
Indeed, agree. For cgroup storage, we could have a per-cpu version
for the new mechanism so it can replace the old one as well.
Will look into this after non per-cpu version is done.
next prev parent reply other threads:[~2022-10-18 18:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 4:56 [PATCH bpf-next 0/5] bpf: Implement cgroup local storage available to non-cgroup-attached bpf progs Yonghong Song
2022-10-14 4:56 ` [PATCH bpf-next 1/5] bpf: Make struct cgroup btf id global Yonghong Song
2022-10-14 4:56 ` [PATCH bpf-next 2/5] bpf: Implement cgroup storage available to non-cgroup-attached bpf progs Yonghong Song
2022-10-17 18:01 ` sdf
2022-10-17 18:25 ` Yosry Ahmed
2022-10-17 18:43 ` Stanislav Fomichev
2022-10-17 18:47 ` Yosry Ahmed
2022-10-17 19:07 ` Stanislav Fomichev
2022-10-17 19:11 ` Yosry Ahmed
2022-10-17 19:26 ` Tejun Heo
2022-10-17 21:07 ` Martin KaFai Lau
2022-10-17 21:23 ` Yosry Ahmed
2022-10-17 23:55 ` Martin KaFai Lau
2022-10-18 0:47 ` Yosry Ahmed
2022-10-17 22:16 ` sdf
2022-10-18 0:52 ` Martin KaFai Lau
2022-10-18 5:59 ` Yonghong Song
2022-10-18 17:08 ` sdf
2022-10-18 17:17 ` Alexei Starovoitov
2022-10-18 18:08 ` Martin KaFai Lau
2022-10-18 18:11 ` Yosry Ahmed
2022-10-18 18:26 ` Yonghong Song [this message]
2022-10-18 23:12 ` Andrii Nakryiko
2022-10-17 20:15 ` Yonghong Song
2022-10-17 20:18 ` Yosry Ahmed
2022-10-17 20:13 ` Yonghong Song
2022-10-17 20:10 ` Yonghong Song
2022-10-17 20:14 ` Yosry Ahmed
2022-10-17 20:29 ` Yonghong Song
2022-10-17 19:23 ` Yonghong Song
2022-10-17 21:03 ` Stanislav Fomichev
2022-10-17 22:26 ` Martin KaFai Lau
2022-10-17 18:16 ` David Vernet
2022-10-17 19:45 ` Yonghong Song
2022-10-14 4:56 ` [PATCH bpf-next 3/5] libbpf: Support new cgroup local storage Yonghong Song
2022-10-14 4:56 ` [PATCH bpf-next 4/5] bpftool: " Yonghong Song
2022-10-17 10:26 ` Quentin Monnet
2022-10-14 4:56 ` [PATCH bpf-next 5/5] selftests/bpf: Add selftests for " Yonghong Song
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=da3d44e2-4d3e-89f7-35f0-849f6f603f05@meta.com \
--to=yhs@meta.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=tj@kernel.org \
--cc=yhs@fb.com \
--cc=yosryahmed@google.com \
/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