From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: bpf@vger.kernel.org
Cc: andrii@kernel.org, memxor@gmail.com, akpm@linux-foundation.org,
peterz@infradead.org, vbabka@suse.cz, bigeasy@linutronix.de,
rostedt@goodmis.org, houtao1@huawei.com, hannes@cmpxchg.org,
mhocko@suse.com, willy@infradead.org, tglx@linutronix.de,
jannh@google.com, tj@kernel.org, linux-mm@kvack.org,
kernel-team@fb.com
Subject: [PATCH bpf-next v7 0/6] bpf, mm: Introduce try_alloc_pages()
Date: Wed, 12 Feb 2025 09:46:59 -0800 [thread overview]
Message-ID: <20250212174705.44492-1-alexei.starovoitov@gmail.com> (raw)
From: Alexei Starovoitov <ast@kernel.org>
Hi All,
The main motivation is to make alloc page and slab reentrant and
remove bpf_mem_alloc.
v6->v7:
- Took Sebastian's patch for localtry_lock_t as-is with minor
addition of local_trylock_acquire() for proper LOCKDEP.
Kept his authorship.
- Adjusted patch 4 to use it. The rest is unchanged.
v6:
https://lore.kernel.org/bpf/20250124035655.78899-1-alexei.starovoitov@gmail.com/
v5->v6:
- Addressed comments from Sebastian, Vlastimil
- New approach for local_lock_t in patch 3. Instead of unconditionally
increasing local_lock_t size to 4 bytes introduce local_trylock_t
and use _Generic() tricks to manipulate active field.
- Address stackdepot reentrance issues. alloc part in patch 1 and
free part in patch 2.
- Inlined mem_cgroup_cancel_charge() in patch 4 since this helper
is being removed.
- Added Acks.
- Dropped failslab, kfence, kmemleak patch.
- Improved bpf_map_alloc_pages() in patch 6 a bit to demo intended usage.
It will be refactored further.
- Considered using __GFP_COMP in try_alloc_pages to simplify
free_pages_nolock a bit, but then decided to make it work
for all types of pages, since free_pages_nolock() is used by
stackdepot and currently it's using non-compound order 2.
I felt it's best to leave it as-is and make free_pages_nolock()
support all pages.
v5:
https://lore.kernel.org/all/20250115021746.34691-1-alexei.starovoitov@gmail.com/
v4->v5:
- Fixed patch 1 and 4 commit logs and comments per Michal suggestions.
Added Acks.
- Added patch 6 to make failslab, kfence, kmemleak complaint
with trylock mode. It's a prerequisite for reentrant slab patches.
v4:
https://lore.kernel.org/bpf/20250114021922.92609-1-alexei.starovoitov@gmail.com/
v3->v4:
Addressed feedback from Michal and Shakeel:
- GFP_TRYLOCK flag is gone. gfpflags_allow_spinning() is used instead.
- Improved comments and commit logs.
v3:
https://lore.kernel.org/bpf/20241218030720.1602449-1-alexei.starovoitov@gmail.com/
v2->v3:
To address the issues spotted by Sebastian, Vlastimil, Steven:
- Made GFP_TRYLOCK internal to mm/internal.h
try_alloc_pages() and free_pages_nolock() are the only interfaces.
- Since spin_trylock() is not safe in RT from hard IRQ and NMI
disable such usage in lock_trylock and in try_alloc_pages().
In such case free_pages_nolock() falls back to llist right away.
- Process trylock_free_pages llist when preemptible.
- Check for things like unaccepted memory and order <= 3 early.
- Don't call into __alloc_pages_slowpath() at all.
- Inspired by Vlastimil's struct local_tryirq_lock adopted it in
local_lock_t. Extra 4 bytes in !RT in local_lock_t shouldn't
affect any of the current local_lock_t users. This is patch 3.
- Tested with bpf selftests in RT and !RT and realized how much
more work is necessary on bpf side to play nice with RT.
The urgency of this work got higher. The alternative is to
convert bpf bits left and right to bpf_mem_alloc.
v2:
https://lore.kernel.org/bpf/20241210023936.46871-1-alexei.starovoitov@gmail.com/
v1->v2:
- fixed buggy try_alloc_pages_noprof() in PREEMPT_RT. Thanks Peter.
- optimize all paths by doing spin_trylock_irqsave() first
and only then check for gfp_flags & __GFP_TRYLOCK.
Then spin_lock_irqsave() if it's a regular mode.
So new gfp flag will not add performance overhead.
- patches 2-5 are new. They introduce lockless and/or trylock free_pages_nolock()
and memcg support. So it's in usable shape for bpf in patch 6.
v1:
https://lore.kernel.org/bpf/20241116014854.55141-1-alexei.starovoitov@gmail.com/
Alexei Starovoitov (5):
mm, bpf: Introduce try_alloc_pages() for opportunistic page allocation
mm, bpf: Introduce free_pages_nolock()
memcg: Use trylock to access memcg stock_lock.
mm, bpf: Use memcg in try_alloc_pages().
bpf: Use try_alloc_pages() to allocate pages for bpf needs.
Sebastian Andrzej Siewior (1):
locking/local_lock: Introduce localtry_lock_t
include/linux/bpf.h | 2 +-
include/linux/gfp.h | 23 ++++
include/linux/local_lock.h | 59 ++++++++
include/linux/local_lock_internal.h | 123 +++++++++++++++++
include/linux/mm_types.h | 4 +
include/linux/mmzone.h | 3 +
kernel/bpf/arena.c | 5 +-
kernel/bpf/syscall.c | 23 +++-
lib/stackdepot.c | 10 +-
mm/internal.h | 1 +
mm/memcontrol.c | 52 +++++---
mm/page_alloc.c | 200 ++++++++++++++++++++++++++--
mm/page_owner.c | 8 +-
13 files changed, 472 insertions(+), 41 deletions(-)
--
2.43.5
next reply other threads:[~2025-02-12 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 17:46 Alexei Starovoitov [this message]
2025-02-12 17:47 ` [PATCH bpf-next v7 1/6] mm, bpf: Introduce try_alloc_pages() for opportunistic page allocation Alexei Starovoitov
2025-02-12 17:47 ` [PATCH bpf-next v7 2/6] mm, bpf: Introduce free_pages_nolock() Alexei Starovoitov
2025-02-12 17:47 ` [PATCH bpf-next v7 3/6] locking/local_lock: Introduce localtry_lock_t Alexei Starovoitov
2025-02-12 17:47 ` [PATCH bpf-next v7 4/6] memcg: Use trylock to access memcg stock_lock Alexei Starovoitov
2025-02-12 17:47 ` [PATCH bpf-next v7 5/6] mm, bpf: Use memcg in try_alloc_pages() Alexei Starovoitov
2025-02-12 17:47 ` [PATCH bpf-next v7 6/6] bpf: Use try_alloc_pages() to allocate pages for bpf needs Alexei Starovoitov
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=20250212174705.44492-1-alexei.starovoitov@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=houtao1@huawei.com \
--cc=jannh@google.com \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=memxor@gmail.com \
--cc=mhocko@suse.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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