From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, puranjay12@gmail.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v5 0/2] memcg accounting for BPF arena
Date: Fri, 02 Jan 2026 22:40:10 +0000 [thread overview]
Message-ID: <176739361003.4022808.6370687418641185135.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260102200230.25168-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 2 Jan 2026 12:02:26 -0800 you wrote:
> v4: https://lore.kernel.org/all/20260102181333.3033679-1-puranjay@kernel.org/
> Changes in v4->v5:
> - Remove unused variables from bpf_map_alloc_pages() (CI)
>
> v3: https://lore.kernel.org/all/20260102151852.570285-1-puranjay@kernel.org/
> Changes in v3->v4:
> - Do memcg set/recover in arena_reserve_pages() rather than
> bpf_arena_reserve_pages() for symmetry with other kfuncs (Alexei)
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/2] bpf: syscall: Introduce memcg enter/exit helpers
https://git.kernel.org/bpf/bpf-next/c/817593af7b9b
- [bpf-next,v5,2/2] bpf: arena: Reintroduce memcg accounting
https://git.kernel.org/bpf/bpf-next/c/e66fe1bc6d25
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-02 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 20:02 [PATCH bpf-next v5 0/2] memcg accounting for BPF arena Puranjay Mohan
2026-01-02 20:02 ` [PATCH bpf-next v5 1/2] bpf: syscall: Introduce memcg enter/exit helpers Puranjay Mohan
2026-01-02 20:02 ` [PATCH bpf-next v5 2/2] bpf: arena: Reintroduce memcg accounting Puranjay Mohan
2026-01-02 22:40 ` 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=176739361003.4022808.6370687418641185135.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=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=puranjay12@gmail.com \
--cc=puranjay@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