[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <hqd7h7elpou6mohkdr2rqcz6u7xuanezuq3ti56ibsnccsb2d2@yokitckdkwqo>
Date: Tue, 6 May 2025 16:34:55 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Brendan Jackman <jackmanb@...gle.com>
Cc: akpm@...ux-foundation.org, vbabka@...e.cz, surenb@...gle.com,
mhocko@...e.com, hannes@...xchg.org, bp@...en8.de, tglx@...utronix.de,
david@...hat.com, ast@...nel.org, linux-mm@...ck.org, linux-coco@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mm/page_alloc: Ensure try_alloc_pages() plays well
with unaccepted memory
On Tue, May 06, 2025 at 01:20:25PM +0000, Brendan Jackman wrote:
> On Tue May 6, 2025 at 11:25 AM UTC, Kirill A. Shutemov wrote:
> > + /* Bailout, since try_to_accept_memory_one() needs to take a lock */
> > + if (alloc_flags & ALLOC_TRYLOCK)
> > + return false;
> > +
>
> Quick lazy question: why don't we just trylock it like we do for the zone
> lock?
It is not only zone lock. There's also unaccepted_memory_lock inside
accept_memory().
--
Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists