linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: SeongJae Park <sj@kernel.org>,
	Aneesh Kumar <AneeshKumar.KizhakeVeetil@arm.com>,
	David Hildenbrand <david@redhat.com>,
	John Hubbard <jhubbard@nvidia.com>,
	Kirill Shutemov <k.shutemov@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	Mel Gorman <mel.gorman@gmail.com>,
	"Rao, Bharata Bhasker" <bharata@amd.com>,
	Rik van Riel <riel@surriel.com>,
	RaghavendraKT <Raghavendra.KodsaraThimmappa@amd.com>,
	Wei Xu <weixugc@google.com>, Suyeon Lee <leesuyeon0506@gmail.com>,
	Lei Chen <leillc@google.com>,
	"Shukla, Santosh" <santosh.shukla@amd.com>,
	"Grimm, Jon" <jon.grimm@amd.com>,
	shy828301@gmail.com, Zi Yan <ziy@nvidia.com>,
	Liam Howlett <liam.howlett@oracle.com>,
	Gregory Price <gregory.price@memverge.com>,
	linux-mm@kvack.org
Subject: Re: Slow-tier Page Promotion discussion recap and open questions
Date: Wed, 18 Dec 2024 11:23:47 -0800	[thread overview]
Message-ID: <20241218192347.49227-1-sj@kernel.org> (raw)
In-Reply-To: <6d582bb6-3ba5-1768-92f2-6025340a3cd4@google.com>

On Tue, 17 Dec 2024 20:19:56 -0800 (PST) David Rientjes <rientjes@google.com> wrote:

> Hi everybody,
> 
> We had a very interactive discussion last week led by RaghavendraKT on
> slow-tier page promotion intended for memory tiering platforms, thank
> you!  Thanks as well to everybody who attended and provided great
> questions, suggestions, and feedback.
> 
> The RFC patch series "mm: slowtier page promotion based on PTE A bit"[1]
> is a proposal to allow for asynchronous page promotion based on memory
> accesses as an alternative to NUMA Balancing based promotions.  There was
> widespread interest in this topic and the discussion surfaced multiple
> use cases and requirements, very focused on CXL use cases.

Thank you for keeping the series and this great summary, David :)

[...]
> ----->o-----
> I followed up on a discussion point early in the talk about whether this
> should be virtual address scanning like the current approach, walking
> mm_struct's, or the alternative approach which would be physical address
> scanning.
> 
> Raghu sees this as a fully alternative approach such as what DAMON uses
> that is based on rmap.  The only advantage appears to be avoiding
> scanning on top tier memory completely.

IMHO, there could be more advantages of physical address space based
appraoches.  Easier handling of unmapped pages and short-lived processes,
applying different access monitoring / promotion policies for differnt NUMA
nodes (tiers) are some of those off the top of my head.

> 
> ----->o-----
> Wei noted there was a lot of similarities between the RFC implementation
> and the MGLRU page walk functionality and whether it would make sense to
> try to converge these together or make more generally useful.
> 
> SeongJae noted that if DAMON logic were used for the scanning that we
> could re-use the existing support for controlling the overhead.

Just to clarify.  I added this comment since there were concerns around rmap
overhead for pysical address space-based monitoring approaches.

[...]
> My takeaways:
[...]
>  - I think virtual memory scanning is likely the only viable approach for
>    this purpose and we could store state in the underlying struct page,
>    similar to NUMA Balancing, but that all scanning should be driven by
>    walking the mm_struct's to harvest the Accessed bit

I don't clearly get why you think virtual memory scanning is the only viable
approach.  I'm curious if you have some pros/cons list about virtual vs
physical address based appraoches in your mind, and willing to share.

[...]
> We'll be looking to incorporate this discussion in our upstream Memory
> Tiering Working Group to accelerate alignment and progress on the
> approach.

Thank you again for your efforts on this!


Thanks,
SJ

[...]


  parent reply	other threads:[~2024-12-18 19:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18  4:19 David Rientjes
2024-12-18 14:50 ` Zi Yan
2024-12-19  6:38   ` Shivank Garg
2024-12-30  5:30     ` David Rientjes
2024-12-30 17:33       ` Zi Yan
2025-01-06  9:14       ` Shivank Garg
2024-12-18 15:21 ` Nadav Amit
2024-12-20 11:28   ` Raghavendra K T
2024-12-18 19:23 ` SeongJae Park [this message]
2024-12-19  0:56 ` Gregory Price
2024-12-26  1:28   ` Karim Manaouil
2024-12-30  5:36     ` David Rientjes
2024-12-30  6:51       ` Raghavendra K T
2025-01-06 17:02       ` Gregory Price
2024-12-20 11:21 ` Raghavendra K T
2025-01-02  4:44   ` David Rientjes
2025-01-06  6:29     ` Raghavendra K T
2025-01-08  5:43     ` Raghavendra K T

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=20241218192347.49227-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=AneeshKumar.KizhakeVeetil@arm.com \
    --cc=Raghavendra.KodsaraThimmappa@amd.com \
    --cc=bharata@amd.com \
    --cc=david@redhat.com \
    --cc=gregory.price@memverge.com \
    --cc=jhubbard@nvidia.com \
    --cc=jon.grimm@amd.com \
    --cc=k.shutemov@gmail.com \
    --cc=leesuyeon0506@gmail.com \
    --cc=leillc@google.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=mel.gorman@gmail.com \
    --cc=riel@surriel.com \
    --cc=rientjes@google.com \
    --cc=santosh.shukla@amd.com \
    --cc=shy828301@gmail.com \
    --cc=weixugc@google.com \
    --cc=willy@infradead.org \
    --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