[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7ee4fdcf-d773-4279-95f8-fc8300f7fd34@kernel.org>
Date: Fri, 6 Feb 2026 19:57:06 +0100
From: "David Hildenbrand (Arm)" <david@...nel.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: xu.xin16@....com.cn, akpm@...ux-foundation.org, chengming.zhou@...ux.dev,
hughd@...gle.com, wang.yaxin@....com.cn, yang.yang29@....com.cn,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: ksm: initialize rmap values directly and make them const
On 2/6/26 19:49, Matthew Wilcox wrote:
> On Fri, Feb 06, 2026 at 07:09:56PM +0100, David Hildenbrand (Arm) wrote:
>> On 2/6/26 18:34, David Hildenbrand (Arm) wrote:
>>>
>>> Once that changes we can revisit. ACK from me stands.
>>
>> And just to elaborate a bit: I don't see support for > 0 happening any time
>> soon, and it will require significant changes that I am not even sure we
>> would want to maintain upstream :)
>
> OK, you're the KSM maintainer. There doesn't seem to be anywhere else
> in the KSM code which handles large folios, so this is just removing
> code that was recently added?
Yes! Sorry for not being clear. :)
This is a fixup for a patch that introduced that code in the first
place. It will be squashed into the original patch that's not upstream yet.
--
Cheers,
David
Powered by blists - more mailing lists