mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Li Zhe" <lizhe.67@bytedance.com>
To: <nhuhuan@google.com>
Cc: <Liam.Howlett@oracle.com>, <akpm@linux-foundation.org>,
	 <alirad.malek@zptcorp.com>, <anna@kernel.org>,
	<apopple@nvidia.com>,  <bharata@amd.com>, <bp@alien8.de>,
	<byungchul@sk.com>,  <dave.hansen@linux.intel.com>,
	<dave@stgolabs.net>, <david@kernel.org>,
	 <dimitrios.palyvos@zptcorp.com>, <fvdl@google.com>,
	<gourry@gourry.net>,  <hannes@cmpxchg.org>, <hpa@zytor.com>,
	<jackmanb@google.com>,  <jic23@kernel.org>,
	<joshua.hahnjy@gmail.com>,  <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>,  <linux-nfs@vger.kernel.org>,
	<linux-trace-kernel@vger.kernel.org>,  <ljs@kernel.org>,
	<mathieu.desnoyers@efficios.com>,  <matthew.brost@intel.com>,
	<mhiramat@kernel.org>, <mhocko@suse.com>,  <mingo@redhat.com>,
	<nifan.cxl@gmail.com>, <rakie.kim@sk.com>,  <rientjes@google.com>,
	<rkodsara@amd.com>, <rostedt@goodmis.org>,  <rppt@kernel.org>,
	<ryan.roberts@arm.com>, <shivankg@amd.com>,  <sj@kernel.org>,
	<surenb@google.com>, <tglx@kernel.org>,  <trondmy@kernel.org>,
	<vbabka@kernel.org>, <weixugc@google.com>,  <x86@kernel.org>,
	<xuezhengchu@huawei.com>,  <yiannis.nikolakop@gmail.com>,
	<yiannis@zptcorp.com>,  <ying.huang@linux.alibaba.com>,
	<ziy@nvidia.com>
Subject: Re: [RFC PATCH v3 0/3] mm: use non-temporal stores for demotion
Date: Fri,  6 Nov 2026 16:50:19 +0800	[thread overview]
Message-ID: <20261106085019.90487-1-lizhe.67@bytedance.com> (raw)
In-Reply-To: <20261103223025.2482227-1-nhuhuan@google.com>

On Tue, 3 Nov 2026 14:30:22 -0800, Huan Nguyen wrote:

> Using non-temporal stores and prefetching on x86 bypasses CPU cache
> allocation, protecting active workload working sets and improving
> demotion throughput.

Could you show some real workload numbers for this? I am wondering
whether the reduced cache allocation and improved demotion throughput
also translate into visible application-level benefits.

> - Memory ordering:
>   Add a wmb() barrier at the end of folio_mc_copy_nt() to ensure weakly
>   ordered non-temporal stores are drained before page tables are updated.

I have not looked into all the details here, so I may be missing
something. But before migration completes, there should eventually be a
publication step that makes the new folio visible. In theory, that
publication step should already provide the required ordering before
userspace can observe the new folio. So I wonder whether the wmb() in
folio_mc_copy_nt() is really needed here.

Thanks,
Zhe

  parent reply	other threads:[~2026-11-06  8:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 15:02 [PATCH RFC v2 0/3] Demote to lower tier using non-temporal stores Yiannis Nikolakopoulos
2026-07-30 15:02 ` [PATCH RFC v2 1/3] mm, x86: support copying a folio " Yiannis Nikolakopoulos
2026-07-31 21:53   ` Huan Nguyen
2026-08-17 16:34     ` Garg, Shivank
2026-07-30 15:02 ` [PATCH RFC v2 2/3] mm: new migrate_mode flag for async " Yiannis Nikolakopoulos
2026-08-05 14:14   ` Huang, Ying
2026-07-30 15:02 ` [PATCH RFC v2 3/3] mm: use non-temporal stores for demotion Yiannis Nikolakopoulos
2026-07-30 17:30 ` [PATCH RFC v2 0/3] Demote to lower tier using non-temporal stores Gregory Price
2026-07-30 17:40   ` Frank van der Linden
2026-07-30 18:08     ` Johannes Weiner
2026-07-30 20:49       ` Gregory Price
2026-11-03 22:30 ` [RFC PATCH v3 0/3] mm: use non-temporal stores for demotion Huan Nguyen
2026-11-03 22:30   ` [RFC PATCH v3 1/3] mm, x86: support copying a folio using non-temporal stores Huan Nguyen
2026-11-03 22:30   ` [RFC PATCH v3 2/3] mm/migrate: introduce async non-temporal migration mode Huan Nguyen
2026-11-03 22:30   ` [RFC PATCH v3 3/3] mm/vmscan: demote folios using non-temporal stores Huan Nguyen
2026-11-04  0:09   ` [RFC PATCH v3 0/3] mm: use non-temporal stores for demotion Zi Yan
2026-11-12 23:06     ` Huan Nguyen
2026-11-04  9:07   ` Lorenzo Stoakes (ARM)
2026-11-06  8:50   ` Li Zhe [this message]
2026-11-12 22:58     ` Huan Nguyen

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=20261106085019.90487-1-lizhe.67@bytedance.com \
    --to=lizhe.67@bytedance.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alirad.malek@zptcorp.com \
    --cc=anna@kernel.org \
    --cc=apopple@nvidia.com \
    --cc=bharata@amd.com \
    --cc=bp@alien8.de \
    --cc=byungchul@sk.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@stgolabs.net \
    --cc=david@kernel.org \
    --cc=dimitrios.palyvos@zptcorp.com \
    --cc=fvdl@google.com \
    --cc=gourry@gourry.net \
    --cc=hannes@cmpxchg.org \
    --cc=hpa@zytor.com \
    --cc=jackmanb@google.com \
    --cc=jic23@kernel.org \
    --cc=joshua.hahnjy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=matthew.brost@intel.com \
    --cc=mhiramat@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=nhuhuan@google.com \
    --cc=nifan.cxl@gmail.com \
    --cc=rakie.kim@sk.com \
    --cc=rientjes@google.com \
    --cc=rkodsara@amd.com \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=shivankg@amd.com \
    --cc=sj@kernel.org \
    --cc=surenb@google.com \
    --cc=tglx@kernel.org \
    --cc=trondmy@kernel.org \
    --cc=vbabka@kernel.org \
    --cc=weixugc@google.com \
    --cc=x86@kernel.org \
    --cc=xuezhengchu@huawei.com \
    --cc=yiannis.nikolakop@gmail.com \
    --cc=yiannis@zptcorp.com \
    --cc=ying.huang@linux.alibaba.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
all inboxes | Powered by JetHome®