[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQLO=QbXnDBKrDdofpkBg2jESC8rDwi_WiLNOahJQcEWSQ@mail.gmail.com>
Date: Tue, 23 Apr 2024 19:51:17 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Benjamin Tissoires <bentiss@...nel.org>
Cc: Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>, Martin KaFai Lau <martin.lau@...ux.dev>,
Eduard Zingerman <eddyz87@...il.com>, Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>, John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, Stanislav Fomichev <sdf@...gle.com>, Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>, Mykola Lysenko <mykolal@...com>, Shuah Khan <shuah@...nel.org>,
bpf <bpf@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>
Subject: Re: [PATCH bpf-next v2 09/16] bpf: allow struct bpf_wq to be embedded
in arraymaps and hashmaps
On Sat, Apr 20, 2024 at 2:09 AM Benjamin Tissoires <bentiss@...nel.org> wrote:
>
>
> -static void htab_map_free_timers(struct bpf_map *map)
> +static void htab_map_free_timers_and_wq(struct bpf_map *map)
> {
> struct bpf_htab *htab = container_of(map, struct bpf_htab, map);
>
> - /* We only free timer on uref dropping to zero */
> - if (!btf_record_has_field(htab->map.record, BPF_TIMER))
> - return;
> - if (!htab_is_prealloc(htab))
> - htab_free_malloced_timers(htab);
> - else
> - htab_free_prealloced_timers(htab);
> + /* We only free timer and workqueue on uref dropping to zero */
> + if (btf_record_has_field(htab->map.record, BPF_TIMER)) {
> + if (!htab_is_prealloc(htab))
> + htab_free_malloced_timers_or_wq(htab, true);
> + else
> + htab_free_prealloced_timers(htab);
> + }
> + if (btf_record_has_field(htab->map.record, BPF_WORKQUEUE)) {
> + if (!htab_is_prealloc(htab))
> + htab_free_malloced_timers_or_wq(htab, false);
> + else
> + htab_free_prealloced_wq(htab);
> + }
I missed this earlier, but pls follow up to improve this part.
Double walk of all elements once for timer and 2nd for wq
is inefficient. Better to handle it in one go in prealloc and malloced cases.
Until we have delayed_wq it's quite possible that somebody will
have both timers and wq in map elements.
Powered by blists - more mailing lists