From: patchwork-bot+netdevbpf@kernel•org
To: Alexei Starovoitov <alexei.starovoitov@gmail•com>
Cc: davem@davemloft•net, daniel@iogearbox•net, andrii@kernel•org,
netdev@vger•kernel.org, bpf@vger•kernel.org, kernel-team@fb•com
Subject: Re: [PATCH v7 bpf-next 00/11] bpf: Introduce BPF timers.
Date: Thu, 15 Jul 2021 20:40:07 +0000 [thread overview]
Message-ID: <162638160793.17206.8466927115509819243.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210715005417.78572-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 14 Jul 2021 17:54:06 -0700 you wrote:
> From: Alexei Starovoitov <ast@kernel•org>
>
> The first request to support timers in bpf was made in 2013 before sys_bpf syscall
> was added. That use case was periodic sampling. It was address with attaching
> bpf programs to perf_events. Then during XDP development the timers were requested
> to do garbage collection and health checks. They were worked around by implementing
> timers in user space and triggering progs with BPF_PROG_RUN command.
> The user space timers and perf_event+bpf timers are not armed by the bpf program.
> They're done asynchronously vs program execution. The XDP program cannot send a
> packet and arm the timer at the same time. The tracing prog cannot record an
> event and arm the timer right away. This large class of use cases remained
> unaddressed. The jiffy based and hrtimer based timers are essential part of the
> kernel development and with this patch set the hrtimer based timers will be
> available to bpf programs.
>
> [...]
Here is the summary with links:
- [v7,bpf-next,01/11] bpf: Prepare bpf_prog_put() to be called from irq context.
https://git.kernel.org/bpf/bpf-next/c/d809e134be7a
- [v7,bpf-next,02/11] bpf: Factor out bpf_spin_lock into helpers.
https://git.kernel.org/bpf/bpf-next/c/c1b3fed319d3
- [v7,bpf-next,03/11] bpf: Introduce bpf timers.
https://git.kernel.org/bpf/bpf-next/c/b00628b1c7d5
- [v7,bpf-next,04/11] bpf: Add map side support for bpf timers.
https://git.kernel.org/bpf/bpf-next/c/68134668c17f
- [v7,bpf-next,05/11] bpf: Prevent pointer mismatch in bpf_timer_init.
https://git.kernel.org/bpf/bpf-next/c/3e8ce29850f1
- [v7,bpf-next,06/11] bpf: Remember BTF of inner maps.
https://git.kernel.org/bpf/bpf-next/c/40ec00abf1cc
- [v7,bpf-next,07/11] bpf: Relax verifier recursion check.
https://git.kernel.org/bpf/bpf-next/c/86fc6ee6e246
- [v7,bpf-next,08/11] bpf: Implement verifier support for validation of async callbacks.
https://git.kernel.org/bpf/bpf-next/c/bfc6bb74e4f1
- [v7,bpf-next,09/11] bpf: Teach stack depth check about async callbacks.
https://git.kernel.org/bpf/bpf-next/c/7ddc80a476c2
- [v7,bpf-next,10/11] selftests/bpf: Add bpf_timer test.
https://git.kernel.org/bpf/bpf-next/c/3540f7c6b96a
- [v7,bpf-next,11/11] selftests/bpf: Add a test with bpf_timer in inner map.
https://git.kernel.org/bpf/bpf-next/c/61f71e746c72
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-15 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 0:54 [PATCH v7 bpf-next 00/11] bpf: Introduce BPF timers Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 01/11] bpf: Prepare bpf_prog_put() to be called from irq context Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 02/11] bpf: Factor out bpf_spin_lock into helpers Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 03/11] bpf: Introduce bpf timers Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 04/11] bpf: Add map side support for " Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 05/11] bpf: Prevent pointer mismatch in bpf_timer_init Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 06/11] bpf: Remember BTF of inner maps Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 07/11] bpf: Relax verifier recursion check Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 08/11] bpf: Implement verifier support for validation of async callbacks Alexei Starovoitov
2022-01-04 17:15 ` Kris Van Hees
2022-01-04 18:19 ` Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 09/11] bpf: Teach stack depth check about " Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 10/11] selftests/bpf: Add bpf_timer test Alexei Starovoitov
2021-07-15 0:54 ` [PATCH v7 bpf-next 11/11] selftests/bpf: Add a test with bpf_timer in inner map Alexei Starovoitov
2021-07-15 20:40 ` 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=162638160793.17206.8466927115509819243.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=andrii@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=kernel-team@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/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