linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: David Rientjes <rientjes@google.com>
Cc: Fan Ni <nifan.cxl@gmail.com>, Gregory Price <gourry@gourry.net>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Joshua Hahn <joshua.hahnjy@gmail.com>,
	Raghavendra K T <rkodsara@amd.com>,
	"Rao, Bharata Bhasker" <bharata@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>,
	linux-mm@kvack.org
Subject: Re: [Linux Memory Hotness and Promotion] Notes from July 17, 2025
Date: Thu, 31 Jul 2025 10:31:16 -0700	[thread overview]
Message-ID: <20250731173116.jf7bex7evice7zhl@offworld> (raw)
In-Reply-To: <c2f5a8d7-061b-7649-2b9d-03e6314d1102@google.com>

On Tue, 29 Jul 2025, David Rientjes wrote:

>Topics for the next meeting:
>
> - update on status of kpromoted (collector) and kmigrated (promoter)
>   approaches and testing
> - update on sharing Google approach for both to overlap the shared goals
>   and converge where possible
> - discuss proactive demotion interface as an extension to memory.reclaim
>   + possibly leveraging working set extensions on top of MGLRU

fyi the per-node interface to proactive reclaim has also recently been
added.

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b980077899ea49cc747afe003e01ca303b00d463

Thanks,
Davidlohr


      reply	other threads:[~2025-07-31 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  4:11 David Rientjes
2025-07-31 17:31 ` Davidlohr Bueso [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=20250731173116.jf7bex7evice7zhl@offworld \
    --to=dave@stgolabs.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bharata@amd.com \
    --cc=gourry@gourry.net \
    --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