From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
eddyz87@gmail.com, Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH RFC v2 4/5] bpf: add refcnt into struct bpf_async_cb
Date: Thu, 6 Nov 2025 18:48:19 +0100 [thread overview]
Message-ID: <CAP01T77bipYaxBiQ7FG-OzhYOebrmTRKg-k8FZFysqRc7+eRgA@mail.gmail.com> (raw)
In-Reply-To: <20251105-timer_nolock-v2-4-32698db08bfa@meta.com>
On Wed, 5 Nov 2025 at 16:59, Mykyta Yatsenko <mykyta.yatsenko5@gmail.com> wrote:
>
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> To manage lifetime guarantees of the struct bpf_async_cb, when
> no lock serializes mutations, introduce refcnt field into the struct.
> Implement bpf_async_tryget() and bpf_async_put() to handle the refcnt.
>
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
> ---
Acked-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> [...]
next prev parent reply other threads:[~2025-11-06 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:59 [PATCH RFC v2 0/5] bpf: avoid locks in bpf_timer and bpf_wq Mykyta Yatsenko
2025-11-05 15:59 ` [PATCH RFC v2 1/5] bpf: refactor bpf_async_cb callback update Mykyta Yatsenko
2025-11-06 17:03 ` Kumar Kartikeya Dwivedi
2025-11-05 15:59 ` [PATCH RFC v2 2/5] bpf: refactor bpf_async_cb prog swap Mykyta Yatsenko
2025-11-06 16:57 ` Kumar Kartikeya Dwivedi
2025-11-05 15:59 ` [PATCH RFC v2 3/5] bpf: factor out timer deletion helper Mykyta Yatsenko
2025-11-06 16:58 ` Kumar Kartikeya Dwivedi
2025-11-05 15:59 ` [PATCH RFC v2 4/5] bpf: add refcnt into struct bpf_async_cb Mykyta Yatsenko
2025-11-06 17:48 ` Kumar Kartikeya Dwivedi [this message]
2025-11-06 21:41 ` Yonghong Song
2025-11-06 22:36 ` Mykyta Yatsenko
2025-11-05 15:59 ` [PATCH RFC v2 5/5] bpf: remove lock from bpf_async_cb Mykyta Yatsenko
2025-11-06 19:25 ` Kumar Kartikeya Dwivedi
2025-11-07 3:15 ` Alexei Starovoitov
2025-11-07 15:58 ` Mykyta Yatsenko
2025-11-07 20:21 ` Alexei Starovoitov
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=CAP01T77bipYaxBiQ7FG-OzhYOebrmTRKg-k8FZFysqRc7+eRgA@mail.gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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;
as well as URLs for NNTP newsgroup(s).