All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, daniel@iogearbox.net
Subject: Re: [RESEND PATCH bpf-next v6 0/7] Make sleepable arena paths use sleepable alloc_pages
Date: Fri, 02 Oct 2026 13:10:08 +0000	[thread overview]
Message-ID: <179094660853.3409201.15855834832486252230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261002105218.6171-1-emil@etsalapatis.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri,  2 Oct 2026 10:52:11 +0000 you wrote:
> The arena_alloc_pages() call takes a sleepable argument based on whether
> its caller is a sleepable BPF function. This flag, along with the context
> the kfunc is called in, decides whether the call will try to fulfill the
> allocation using the regular or the _nolock variant of the alloc_pages
> API, by means of bpf_map_alloc_pages().
> 
> However, the arena_alloc_pages() call currently only makes allocations
> inside an IRQ-disabled critical section. This forces all allocations to
> use the _nolock() API, which may eagerly fail where the regular variant
> would eventually succeed. There have been reports of this happening for
> sched-ext schedulers.
> 
> [...]

Here is the summary with links:
  - [RESEND,bpf-next,v6,1/7] bpf: Use an llist for page allocations
    https://git.kernel.org/bpf/bpf-next/c/11de29f38a34
  - [RESEND,bpf-next,v6,2/7] bpf: Add sleepable argument to bpf_alloc_pages()
    https://git.kernel.org/bpf/bpf-next/c/cbe7d2bf7355
  - [RESEND,bpf-next,v6,3/7] bpf: Add sleepable arena page allocation path
    https://git.kernel.org/bpf/bpf-next/c/5316ede1f5d0
  - [RESEND,bpf-next,v6,4/7] selftests/bpf: Test large allocations for both sleepable/nonsleepable arena users
    https://git.kernel.org/bpf/bpf-next/c/0f6512272538
  - [RESEND,bpf-next,v6,5/7] bpf: Directly store kfunc desc index in instruction off field
    https://git.kernel.org/bpf/bpf-next/c/baf4e66f038f
  - [RESEND,bpf-next,v6,6/7] bpf: Support per-call-site kfunc specialization
    https://git.kernel.org/bpf/bpf-next/c/23290213e1ab
  - [RESEND,bpf-next,v6,7/7] selftests/bpf: Test per-call site function specialization
    https://git.kernel.org/bpf/bpf-next/c/fc38f07781ca

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-10-02 13:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 10:52 [RESEND PATCH bpf-next v6 0/7] Make sleepable arena paths use sleepable alloc_pages Emil Tsalapatis
2026-10-02 10:52 ` [RESEND PATCH bpf-next v6 1/7] bpf: Use an llist for page allocations Emil Tsalapatis
2026-10-02 10:52 ` [RESEND PATCH bpf-next v6 2/7] bpf: Add sleepable argument to bpf_alloc_pages() Emil Tsalapatis
2026-10-02 10:52 ` [RESEND PATCH bpf-next v6 3/7] bpf: Add sleepable arena page allocation path Emil Tsalapatis
2026-10-02 10:52 ` [RESEND PATCH bpf-next v6 4/7] selftests/bpf: Test large allocations for both sleepable/nonsleepable arena users Emil Tsalapatis
2026-10-02 10:52 ` [RESEND PATCH bpf-next v6 5/7] bpf: Directly store kfunc desc index in instruction off field Emil Tsalapatis
2026-10-02 11:06   ` sashiko-bot
2026-10-02 11:47   ` bot+bpf-ci
2026-10-02 10:52 ` [RESEND PATCH bpf-next v6 6/7] bpf: Support per-call-site kfunc specialization Emil Tsalapatis
2026-10-02 10:52 ` [RESEND PATCH bpf-next v6 7/7] selftests/bpf: Test per-call site function specialization Emil Tsalapatis
2026-10-02 13: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=179094660853.3409201.15855834832486252230.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=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=memxor@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.