From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@kernel.org, eddyz87@gmail.com,
tj@kernel.org, emil@etsalapatis.com, brho@google.com,
joshdon@google.com, dohyunkim@google.com, kkd@meta.com,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 0/2] Timed may_goto
Date: Tue, 04 Mar 2025 02:10:30 +0000 [thread overview]
Message-ID: <174105423050.3834266.5937070565519145279.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250304003239.2390751-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 3 Mar 2025 16:32:37 -0800 you wrote:
> This series replaces the current implementation of cond_break, which
> uses the may_goto instruction, and counts 8 million iterations per stack
> frame, with an implementation based on sampling time locally on the CPU.
>
> This is done to permit a longer time for a given loop per-program
> invocation. The accounting is still done per-stack frame, but the count
> is used to instead amortize the cost of the logic to sample and check
> the time spent since the start.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Add verifier support for timed may_goto
https://git.kernel.org/bpf/bpf-next/c/13a664f46e34
- [bpf-next,v2,2/2] bpf, x86: Add x86 JIT support for timed may_goto
https://git.kernel.org/bpf/bpf-next/c/2cb0a5215274
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:[~2025-03-04 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 0:32 [PATCH bpf-next v2 0/2] Timed may_goto Kumar Kartikeya Dwivedi
2025-03-04 0:32 ` [PATCH bpf-next v2 1/2] bpf: Add verifier support for timed may_goto Kumar Kartikeya Dwivedi
2025-03-04 2:04 ` Alexei Starovoitov
2025-03-04 0:32 ` [PATCH bpf-next v2 2/2] bpf, x86: Add x86 JIT " Kumar Kartikeya Dwivedi
2025-03-04 2:10 ` 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=174105423050.3834266.5937070565519145279.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=brho@google.com \
--cc=daniel@iogearbox.net \
--cc=dohyunkim@google.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=joshdon@google.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=tj@kernel.org \
/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