From: Peter Zijlstra <peterz@infradead.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, memxor@gmail.com,
akpm@linux-foundation.org, vbabka@suse.cz, houtao1@huawei.com,
hannes@cmpxchg.org, shakeel.butt@linux.dev, mhocko@suse.com,
tj@kernel.org, linux-mm@kvack.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 1/2] mm, bpf: Introduce __GFP_TRYLOCK for opportunistic page allocation
Date: Sat, 16 Nov 2024 20:42:02 +0100 [thread overview]
Message-ID: <20241116194202.GR22801@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241116014854.55141-1-alexei.starovoitov@gmail.com>
On Fri, Nov 15, 2024 at 05:48:53PM -0800, Alexei Starovoitov wrote:
> +static inline struct page *try_alloc_page_noprof(int nid)
> +{
> + /* If spin_locks are not held and interrupts are enabled, use normal path. */
> + if (preemptible())
> + return alloc_pages_node_noprof(nid, GFP_NOWAIT | __GFP_ZERO, 0);
This isn't right for PREEMPT_RT, spinlock_t will be preemptible, but you
very much do not want regular allocation calls while inside the
allocator itself for example.
> + /*
> + * Best effort allocation from percpu free list.
> + * If it's empty attempt to spin_trylock zone->lock.
> + * Do not specify __GFP_KSWAPD_RECLAIM to avoid wakeup_kswapd
> + * that may need to grab a lock.
> + * Do not specify __GFP_ACCOUNT to avoid local_lock.
> + * Do not warn either.
> + */
> + return alloc_pages_node_noprof(nid, __GFP_TRYLOCK | __GFP_NOWARN | __GFP_ZERO, 0);
> +}
next prev parent reply other threads:[~2024-11-16 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 1:48 Alexei Starovoitov
2024-11-16 1:48 ` [PATCH bpf-next 2/2] bpf: Use try_alloc_page() to allocate pages for bpf needs Alexei Starovoitov
2024-11-16 19:42 ` Peter Zijlstra [this message]
2024-11-16 21:13 ` [PATCH bpf-next 1/2] mm, bpf: Introduce __GFP_TRYLOCK for opportunistic page allocation Alexei Starovoitov
2024-11-16 21:34 ` Alexei Starovoitov
2024-11-16 21:41 ` Alexei Starovoitov
2024-11-17 10:54 ` Peter Zijlstra
2024-11-17 10:50 ` Peter Zijlstra
2024-11-17 10:54 ` Vlastimil Babka
2024-11-19 0:40 ` 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=20241116194202.GR22801@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=houtao1@huawei.com \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=memxor@gmail.com \
--cc=mhocko@suse.com \
--cc=shakeel.butt@linux.dev \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
/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