[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11025f1c-88d3-41a9-8290-21a9565e9bc3@kernel.org>
Date: Thu, 18 Dec 2025 10:33:16 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Vernon Yang <vernon2gm@...il.com>, akpm@...ux-foundation.org,
lorenzo.stoakes@...cle.com
Cc: ziy@...dia.com, npache@...hat.com, baohua@...nel.org,
lance.yang@...ux.dev, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Vernon Yang <yanglincheng@...inos.cn>
Subject: Re: [PATCH 4/4] mm: khugepaged: set to next mm direct when mm has
MMF_DISABLE_THP_COMPLETELY
On 12/15/25 10:04, Vernon Yang wrote:
> When an mm with the MMF_DISABLE_THP_COMPLETELY flag is detected during
> scanning, directly set khugepaged_scan.mm_slot to the next mm_slot,
> reduce redundant operation.
That conceptually makes sense to me. How much does that safe in
practice? Do you have some performance numbers for processes with rather
large number of VMAs?
--
Cheers
David
Powered by blists - more mailing lists