linux-kernel - Re: [PATCH next 0/2] THP COW support for private executable file mmap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <c0ceb2104cac497383f7f7e5e7a00930@huawei.com>
Date: Tue, 16 Dec 2025 02:12:10 +0000
From: zhangqilong <zhangqilong3@...wei.com>
To: Matthew Wilcox <willy@...radead.org>
CC: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"david@...nel.org" <david@...nel.org>, "lorenzo.stoakes@...cle.com"
	<lorenzo.stoakes@...cle.com>, "corbet@....net" <corbet@....net>,
	"ziy@...dia.com" <ziy@...dia.com>, "baolin.wang@...ux.alibaba.com"
	<baolin.wang@...ux.alibaba.com>, "Liam.Howlett@...cle.com"
	<Liam.Howlett@...cle.com>, "npache@...hat.com" <npache@...hat.com>,
	"ryan.roberts@....com" <ryan.roberts@....com>, "dev.jain@....com"
	<dev.jain@....com>, "baohua@...nel.org" <baohua@...nel.org>,
	"lance.yang@...ux.dev" <lance.yang@...ux.dev>, "vbabka@...e.cz"
	<vbabka@...e.cz>, "rppt@...nel.org" <rppt@...nel.org>, "surenb@...gle.com"
	<surenb@...gle.com>, "mhocko@...e.com" <mhocko@...e.com>, "Wangkefeng (OS
 Kernel Lab)" <wangkefeng.wang@...wei.com>, Sunnanyong
	<sunnanyong@...wei.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH next 0/2] THP COW support for private executable file mmap

> On Mon, Dec 15, 2025 at 08:34:05PM +0800, Zhang Qilong wrote:
> > This patch series implementate THP COW for private executable file
> > mmap. It's major designed to increase the iTLB cache hit rate for hot
> > patching application, and we add a new sysfs knob to disable or enable
> > it.
> 
> You're going to have to provide data to get this patch in.  We've deliberately
> not done this in the past due to memory consumption overhead.

Year, memory consumption overhead is a serious issue, we will conduct a careful evaluation

> So you need to prove that's now the wrong decision to make.
> 
> Microbenchmarks would be a bare minimum, but what are really needed are
> numbers from actual workloads.

Okay, I'm also trying to gather some test data locally(include microbenchmarks and actual workloads).
I'll attach the results once I have finished. Thank you for your suggestion.

--
Thanks,

Zhang