From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ardb@kernel.org, catalin.marinas@arm.com, will@kernel.org,
daniel@iogearbox.net, ast@kernel.org, zlim.lnx@gmail.com,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
andreyknvl@gmail.com, vincenzo.frascino@arm.com,
mark.rutland@arm.com, samitolvanen@google.com,
joey.gouly@arm.com, maz@kernel.org, daizhiyuan@phytium.com.cn,
jthierry@redhat.com, tiantao6@hisilicon.com, pcc@google.com,
akpm@linux-foundation.org, rppt@kernel.org,
Jisheng.Zhang@synaptics.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 0/2] arm64/bpf: remove 128MB limit for BPF JIT programs
Date: Mon, 08 Nov 2021 21:30:07 +0000 [thread overview]
Message-ID: <163640700729.18756.3678999671690416622.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1636131046-5982-1-git-send-email-alan.maguire@oracle.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 5 Nov 2021 16:50:44 +0000 you wrote:
> There is a 128MB limit on BPF JIT program allocations; this is
> to ensure BPF programs are in branching range of each other.
> Patch 1 in this series removes this restriction. To verify
> exception handling still works, a test case to validate
> exception handling in BPF programs is added in patch 2.
>
> There was previous discussion around this topic [1], in particular
> would be good to get feedback from Daniel if this approach makes
> sense.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/2] arm64/bpf: remove 128MB limit for BPF JIT programs
https://git.kernel.org/bpf/bpf-next/c/b89ddf4cca43
- [v2,bpf-next,2/2] selftests/bpf: add exception handling selftests for tp_bpf program
https://git.kernel.org/bpf/bpf-next/c/c23551c9c36a
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-11-08 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 16:50 [PATCH v2 bpf-next 0/2] arm64/bpf: remove 128MB limit for BPF JIT programs Alan Maguire
2021-11-05 16:50 ` [PATCH v2 bpf-next 1/2] " Alan Maguire
2021-11-05 16:50 ` [PATCH v2 bpf-next 2/2] selftests/bpf: add exception handling selftests for tp_bpf program Alan Maguire
2021-11-05 18:54 ` Andrii Nakryiko
2021-11-08 21: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=163640700729.18756.3678999671690416622.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=andreyknvl@gmail.com \
--cc=andrii@kernel.org \
--cc=ardb@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daizhiyuan@phytium.com.cn \
--cc=daniel@iogearbox.net \
--cc=joey.gouly@arm.com \
--cc=john.fastabend@gmail.com \
--cc=jthierry@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pcc@google.com \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=songliubraving@fb.com \
--cc=tiantao6@hisilicon.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
--cc=yhs@fb.com \
--cc=zlim.lnx@gmail.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