From: patchwork-bot+netdevbpf@kernel.org
To: Joanne Koong <joannekoong@fb.com>
Cc: bpf@vger.kernel.org, kafai@fb.com, kpsingh@kernel.org,
memxor@gmail.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, tj@kernel.org, davemarchevsky@fb.com,
joannelkoong@gmail.com
Subject: Re: [PATCH bpf-next v3 0/2] Enable non-atomic allocations in local storage
Date: Mon, 21 Mar 2022 02:00:10 +0000 [thread overview]
Message-ID: <164782801058.32327.2805354676305440542.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220318045553.3091807-1-joannekoong@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 17 Mar 2022 21:55:51 -0700 you wrote:
> From: Joanne Koong <joannelkoong@gmail.com>
>
> Currently, local storage memory can only be allocated atomically
> (GFP_ATOMIC). This restriction is too strict for sleepable bpf
> programs.
>
> In this patchset, sleepable programs can allocate memory in local
> storage using GFP_KERNEL, while non-sleepable programs always default to
> GFP_ATOMIC.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Enable non-atomic allocations in local storage
https://git.kernel.org/bpf/bpf-next/c/b00fa38a9c1c
- [bpf-next,v3,2/2] selftests/bpf: Test for associating multiple elements with the local storage
https://git.kernel.org/bpf/bpf-next/c/0e790cbb1af9
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:[~2022-03-21 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 4:55 [PATCH bpf-next v3 0/2] Enable non-atomic allocations in local storage Joanne Koong
2022-03-18 4:55 ` [PATCH bpf-next v3 1/2] bpf: " Joanne Koong
2022-03-18 4:55 ` [PATCH bpf-next v3 2/2] selftests/bpf: Test for associating multiple elements with the " Joanne Koong
2022-03-21 2: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=164782801058.32327.2805354676305440542.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=davemarchevsky@fb.com \
--cc=joannekoong@fb.com \
--cc=joannelkoong@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@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