BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mike Rapoport <rppt@kernel.org>
Cc: ast@kernel.org, andrii@kernel.org, bp@alien8.de,
	daniel@iogearbox.net, dave.hansen@linux.intel.com,
	eddyz87@gmail.com, mingo@redhat.com, memxor@gmail.com,
	song@kernel.org, tglx@kernel.org, emil@etsalapatis.com,
	hpa@zytor.com, jolsa@kernel.org, john.fastabend@gmail.com,
	martin.lau@linux.dev, yonghong.song@linux.dev,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, olsajiri@gmail.com
Subject: Re: [PATCH] x86/bpf: make arch_bpf_trampoline_size allocate from EXECMEM_MODULE_DATA
Date: Thu, 20 Aug 2026 16:00:06 +0000	[thread overview]
Message-ID: <178724160664.341736.16028923311216598674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260818130510.3110054-1-rppt@kernel.org>

Hello:

This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Tue, 18 Aug 2026 16:05:10 +0300 you wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
> 
> Jiri Olsa reports slowdown of tracing_multi benchmark that allocates huge
> number of trampolines [1].
> 
> The slowdown caused by extra protection changes in execmem_alloc_rw() and
> execmem_free().
> 
> [...]

Here is the summary with links:
  - x86/bpf: make arch_bpf_trampoline_size allocate from EXECMEM_MODULE_DATA
    https://git.kernel.org/bpf/bpf/c/c7a2a3618290

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-08-20 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 13:05 [PATCH] x86/bpf: make arch_bpf_trampoline_size allocate from EXECMEM_MODULE_DATA Mike Rapoport
2026-08-18 14:07 ` bot+bpf-ci
2026-08-19  6:42   ` Mike Rapoport
2026-08-19  7:34     ` Daniel Borkmann
2026-08-18 20:51 ` Jiri Olsa
2026-08-20 16:00 ` 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=178724160664.341736.16028923311216598674.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=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=hpa@zytor.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=mingo@redhat.com \
    --cc=olsajiri@gmail.com \
    --cc=rppt@kernel.org \
    --cc=song@kernel.org \
    --cc=tglx@kernel.org \
    --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