From: Bharata B Rao <bharata@amd.com>
To: David Rientjes <rientjes@google.com>,
Davidlohr Bueso <dave@stgolabs.net>, Fan Ni <nifan.cxl@gmail.com>,
Frank van der Linden <fvdl@google.com>,
"Gregory Price" <gourry@gourry.net>,
Jonathan Cameron <jic23@kernel.org>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Raghavendra K T <rkodsara@amd.com>, SeongJae Park <sj@kernel.org>,
Wei Xu <weixugc@google.com>,
Xuezheng Chu <xuezhengchu@huawei.com>,
Yiannis Nikolakopoulos <yiannis@zptcorp.com>,
"Zi Yan" <ziy@nvidia.com>
Cc: <linux-mm@kvack.org>
Subject: Re: [Linux Memory Hotness and Promotion] Notes from September 24, 2026
Date: Sun, 27 Sep 2026 21:26:19 +0530 [thread overview]
Message-ID: <e327855e-3a3a-4bc3-afb2-4f241a92adcb@amd.com> (raw)
In-Reply-To: <0c8a7227-c7eb-bef1-7326-c7b04cde78a8@google.com>
On 27-Sep-26 3:13 AM, David Rientjes wrote:
>
> Bharata, have you thought about the possibility of only introducing the
> asynchronous promotion support first, getting alignment from stakeholders
> on that, and then extending pghot with additional enhancements later?
I have gone down that route earlier [1] but we can always revisit and resurrect
the effort if required.
As discussed during the call, I think it would be good to have a dedicated F2F
meeting or BoF during LPC to reach to some conclusion/consensus.
[1] https://lore.kernel.org/linux-mm/20250616133931.206626-1-bharata@amd.com/#t
Regards,
Bharata.
prev parent reply other threads:[~2026-09-27 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 21:43 [Linux Memory Hotness and Promotion] Notes from September 24, 2026 David Rientjes
2026-09-27 15:56 ` Bharata B Rao [this message]
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=e327855e-3a3a-4bc3-afb2-4f241a92adcb@amd.com \
--to=bharata@amd.com \
--cc=dave@stgolabs.net \
--cc=fvdl@google.com \
--cc=gourry@gourry.net \
--cc=jic23@kernel.org \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-mm@kvack.org \
--cc=nifan.cxl@gmail.com \
--cc=rientjes@google.com \
--cc=rkodsara@amd.com \
--cc=sj@kernel.org \
--cc=weixugc@google.com \
--cc=xuezhengchu@huawei.com \
--cc=yiannis@zptcorp.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