From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@suse.com>
Cc: Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Filipe Manana <fdmanana@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm, percpu: do not consider sleepable allocations atomic
Date: Wed, 5 Mar 2025 16:35:07 +0100 [thread overview]
Message-ID: <edda21bc-0dfe-4fd9-81e6-705095de9b1b@suse.cz> (raw)
In-Reply-To: <Z8hpWSsDuMX1salt@tiehlicka>
On 3/5/25 16:10, Michal Hocko wrote:
> Sorry, I have missed follow ups here.
>
>> I assume it's probably not easy to
>> implement as page table allocations are involved in the process and we don't
>> have a way to supply preallocated memory for those.
>
> Why would this be a concern if the allocation is done outside of the
> lock?
It's not a concern if it can be done outside of the lock. I don't know the
code enough to see if it's feasible. There's e.g. pcpu_populate_chunk()
ending up doing vmap_pages_range_noflush() that AFAIK means page table
allocations. Can it be done outside of the lock?
next prev parent reply other threads:[~2025-03-05 19:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 12:26 Michal Hocko
2025-02-11 15:05 ` Vlastimil Babka
2025-02-11 20:55 ` Tejun Heo
2025-02-12 16:57 ` Michal Hocko
2025-02-12 18:14 ` Tejun Heo
2025-02-12 20:53 ` Michal Hocko
2025-02-12 21:30 ` Tejun Heo
2025-02-12 21:39 ` Dennis Zhou
2025-02-14 15:52 ` Michal Hocko
2025-02-21 2:36 ` Dennis Zhou
2025-02-21 9:48 ` Vlastimil Babka
2025-03-05 15:10 ` Michal Hocko
2025-03-05 15:35 ` Vlastimil Babka [this message]
2025-02-14 15:43 ` Michal Hocko
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=edda21bc-0dfe-4fd9-81e6-705095de9b1b@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=dennis@kernel.org \
--cc=fdmanana@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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