[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <563a6f8f-7a8b-40a8-a553-a51c3e4b9a28@kernel.org>
Date: Wed, 7 Jan 2026 23:06:38 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Ankur Arora <ankur.a.arora@...cle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, x86@...nel.org
Cc: akpm@...ux-foundation.org, bp@...en8.de, dave.hansen@...ux.intel.com,
hpa@...or.com, mingo@...hat.com, mjguzik@...il.com, luto@...nel.org,
peterz@...radead.org, tglx@...utronix.de, willy@...radead.org,
raghavendra.kt@....com, chleroy@...nel.org, ioworker0@...il.com,
lizhe.67@...edance.com, boris.ostrovsky@...cle.com, konrad.wilk@...cle.com
Subject: Re: [PATCH v11 2/8] mm: introduce clear_pages() and
clear_user_pages()
On 1/7/26 08:20, Ankur Arora wrote:
> Introduce clear_pages(), to be overridden by architectures that
> support more efficient clearing of consecutive pages.
>
> Also introduce clear_user_pages(), however, we will not expect this
> function to be overridden anytime soon.
>
> As we do for clear_user_page(), define clear_user_pages() only if the
> architecture does not define clear_user_highpage().
>
> That is because if the architecture does define clear_user_highpage(),
> then it likely needs some flushing magic when clearing user pages or
> highpages. This means we can get away without defining clear_user_pages(),
> since, much like its single page sibling, its only potential user is the
> generic clear_user_highpages() which should instead be using
> clear_user_highpage().
>
> Signed-off-by: Ankur Arora <ankur.a.arora@...cle.com>
> ---
Acked-by: David Hildenbrand (Red Hat) <david@...nel.org>
--
Cheers
David
Powered by blists - more mailing lists