BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
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,
	memxor@gmail.com, eddyz87@gmail.com, yatsenko@meta.com
Subject: Re: [PATCH bpf-next v6 00/10] bpf: Avoid locks in bpf_timer and bpf_wq
Date: Wed, 21 Jan 2026 02:30:08 +0000	[thread overview]
Message-ID: <176896260860.696500.15496590516058993754.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120-timer_nolock-v6-0-670ffdd787b4@meta.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue, 20 Jan 2026 15:59:09 +0000 you wrote:
> This series reworks implementation of BPF timer and workqueue APIs.
> The goal is to make both timers and wq non-blocking, enabling their use
> in NMI context.
> Today this code relies on a bpf_spin_lock embedded in the map element to
> serialize:
>  * init of the async object,
>  * setting/changing the callback and bpf_prog
>  * starting/cancelling the timer/work
>  * tearing down when the map element is deleted or the map’s user ref is
>  dropped
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,01/10] bpf: Factor out timer deletion helper
    https://git.kernel.org/bpf/bpf-next/c/c1f2c449de27
  - [bpf-next,v6,02/10] bpf: Remove unnecessary arguments from bpf_async_set_callback()
    https://git.kernel.org/bpf/bpf-next/c/57d31e72dbdd
  - [bpf-next,v6,03/10] bpf: Introduce lock-free bpf_async_update_prog_callback()
    https://git.kernel.org/bpf/bpf-next/c/8bb1e32b3fac
  - [bpf-next,v6,04/10] bpf: Simplify bpf_timer_cancel()
    https://git.kernel.org/bpf/bpf-next/c/83c9030cdc45
  - [bpf-next,v6,05/10] bpf: Enable bpf timer and workqueue use in NMI
    (no matching commit)
  - [bpf-next,v6,06/10] bpf: Add verifier support for bpf_timer argument in kfuncs
    (no matching commit)
  - [bpf-next,v6,07/10] bpf: Introduce bpf_timer_cancel_async() kfunc
    (no matching commit)
  - [bpf-next,v6,08/10] selftests/bpf: Refactor timer selftests
    (no matching commit)
  - [bpf-next,v6,09/10] selftests/bpf: Add stress test for timer async cancel
    (no matching commit)
  - [bpf-next,v6,10/10] selftests/bpf: Verify bpf_timer_cancel_async works
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-21  2:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 15:59 [PATCH bpf-next v6 00/10] bpf: Avoid locks in bpf_timer and bpf_wq Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 01/10] bpf: Factor out timer deletion helper Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 02/10] bpf: Remove unnecessary arguments from bpf_async_set_callback() Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 03/10] bpf: Introduce lock-free bpf_async_update_prog_callback() Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 04/10] bpf: Simplify bpf_timer_cancel() Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 05/10] bpf: Enable bpf timer and workqueue use in NMI Mykyta Yatsenko
2026-01-20 18:31   ` Andrii Nakryiko
2026-01-20 21:17     ` Mykyta Yatsenko
2026-01-21  0:26       ` Andrii Nakryiko
2026-01-20 15:59 ` [PATCH bpf-next v6 06/10] bpf: Add verifier support for bpf_timer argument in kfuncs Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 07/10] bpf: Introduce bpf_timer_cancel_async() kfunc Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 08/10] selftests/bpf: Refactor timer selftests Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 09/10] selftests/bpf: Add stress test for timer async cancel Mykyta Yatsenko
2026-01-20 15:59 ` [PATCH bpf-next v6 10/10] selftests/bpf: Verify bpf_timer_cancel_async works Mykyta Yatsenko
2026-01-21  2:30 ` patchwork-bot+netdevbpf [this message]

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=176896260860.696500.15496590516058993754.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=memxor@gmail.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