From: Matthew Wilcox <willy@infradead.org>
To: Zhang Qilong <zhangqilong3@huawei.com>
Cc: akpm@linux-foundation.org, david@kernel.org,
lorenzo.stoakes@oracle.com, corbet@lwn.net, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, vbabka@suse.cz,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
wangkefeng.wang@huawei.com, sunnanyong@huawei.com,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, lianux.mm@gmail.com
Subject: Re: [PATCH next v2 0/2] THP COW support for private executable file mmap
Date: Sun, 28 Dec 2025 03:42:40 +0000 [thread overview]
Message-ID: <aVCnMI5gFLTB9UCe@casper.infradead.org> (raw)
In-Reply-To: <20251226100337.4171191-1-zhangqilong3@huawei.com>
On Fri, Dec 26, 2025 at 06:03:35PM +0800, Zhang Qilong wrote:
> The MySQL (Ver 8.0.25) test results on AMD are as follows:
>
> -------------------------------------------------------------------
> | Exec mmap Rss(kB) | Measured tpmC (NewOrders) |
> -----------------|--------------------|---------------------------|
> base(page COW) | 32868 | 339686 |
> -----------------|--------------------|---------------------------|
> exec THP COW | 43516 | 371324 |
> -------------------------------------------------------------------
>
> The MySQL using exec THP COW consumes an additional 10648 kB of memory
> but achieves 9.3% performance improvement in the scenario of hotpatch.
> Additionally, another our internal program achieves approximately a 5%
> performance improvement as well.
>
> As result, using exec THP COW will consume additional memory. The
> additional memory consumption may be negligible for the current system.
> It's necessary to balance the memory consumption with the performance
> impact.
I mean ... you say "negligible", I saay "32% extra". 9% performance
gain is certainly nothing to sneer at (and is consistent with measured
performance gains from using large folios for, eg, kernel compiles).
But wow, that's a lot of extra memory. My feeling is that we shouldn't
add this functionality, but I'd welcome other opinions.
next prev parent reply other threads:[~2025-12-28 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 10:03 Zhang Qilong
2025-12-26 10:03 ` [PATCH next v2 1/2] mm/huge_memory: Implementation of THP COW for " Zhang Qilong
2025-12-26 10:03 ` [PATCH next v2 2/2] mm/huge_memory: Use per-VMA hugepage flag hints for exec THP COW Zhang Qilong
2025-12-28 3:42 ` Matthew Wilcox [this message]
2025-12-30 21:42 ` [PATCH next v2 0/2] THP COW support for private executable file mmap David Hildenbrand (Red Hat)
2025-12-30 21:39 ` David Hildenbrand (Red Hat)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aVCnMI5gFLTB9UCe@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=lianux.mm@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=sunnanyong@huawei.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=zhangqilong3@huawei.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox