From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: ast@kernel.org, eddyz87@gmail.com, davem@davemloft.net,
dsahern@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 0/2] bpf, x86: inline bpf_get_current_task() for x86_64
Date: Wed, 21 Jan 2026 04:50:07 +0000 [thread overview]
Message-ID: <176897100760.729216.7176451901339575079.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120070555.233486-1-dongml2@chinatelecom.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 20 Jan 2026 15:05:53 +0800 you wrote:
> Inline bpf_get_current_task() and bpf_get_current_task_btf() for x86_64
> to obtain better performance, and add the testcase for it.
>
> Changes since v5:
> * remove unnecessary 'ifdef' and __description in the selftests
> * v5: https://lore.kernel.org/bpf/20260119070246.249499-1-dongml2@chinatelecom.cn/
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/2] bpf, x86: inline bpf_get_current_task() for x86_64
https://git.kernel.org/bpf/bpf-next/c/eaedea154eb9
- [bpf-next,v6,2/2] selftests/bpf: test the jited inline of bpf_get_current_task
https://git.kernel.org/bpf/bpf-next/c/4fca95095cdc
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:[~2026-01-21 4:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 7:05 [PATCH bpf-next v6 0/2] bpf, x86: inline bpf_get_current_task() for x86_64 Menglong Dong
2026-01-20 7:05 ` [PATCH bpf-next v6 1/2] " Menglong Dong
2026-01-21 1:23 ` Andrii Nakryiko
2026-01-21 1:43 ` Alexei Starovoitov
2026-01-21 1:58 ` Menglong Dong
2026-01-21 3:10 ` Alexei Starovoitov
2026-01-21 3:37 ` Menglong Dong
2026-01-21 4:12 ` Andrii Nakryiko
2026-01-21 4:46 ` Alexei Starovoitov
2026-01-21 6:35 ` Andrii Nakryiko
2026-01-20 7:05 ` [PATCH bpf-next v6 2/2] selftests/bpf: test the jited inline of bpf_get_current_task Menglong Dong
2026-01-20 17:52 ` Eduard Zingerman
2026-01-21 1:05 ` Andrii Nakryiko
2026-01-21 1:28 ` Menglong Dong
2026-01-21 1:32 ` Eduard Zingerman
2026-01-21 3:03 ` Menglong Dong
2026-01-21 4:50 ` 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=176897100760.729216.7176451901339575079.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hpa@zytor.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yonghong.song@linux.dev \
/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