From: Raghavendra K T <rkodsara@amd.com>
To: Nadav Amit <nadav.amit@gmail.com>, David Rientjes <rientjes@google.com>
Cc: 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>,
sj@kernel.org, shy828301@gmail.com, Zi Yan <ziy@nvidia.com>,
"Liam R . Howlett" <liam.howlett@oracle.com>,
Gregory Price <gregory.price@memverge.com>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>
Subject: Re: Slow-tier Page Promotion discussion recap and open questions
Date: Fri, 20 Dec 2024 16:58:39 +0530 [thread overview]
Message-ID: <d72d37fb-03d8-45ed-8c4a-d18314049121@amd.com> (raw)
In-Reply-To: <806F5002-00BB-47E9-A265-5CBF2C4CB8A7@gmail.com>
On 12/18/2024 8:51 PM, Nadav Amit wrote:
>
>
>> On 18 Dec 2024, at 6:19, 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.
>>
>
> Just sharing my 2 cents.
>
> IIUC, the suggested approach has two benefits:
>
> 1. Fewer/no page-faults (as A-bit is used to detect usage)
> 2. Batching
>
> While (2) seems like a win that might be added un top of AutoNUMA, (1)
> is more delicate. As indicated in the patch-set, the "exact destination”
> is lost. At the same time, the last time I checked, the A-bit setting
> wasn’t free and cost something like 550 cycles (others saw similar
> results [1]).
>
> So considering empty page-fault is ~1050 cycles (2014 number Linus
> measured [2]), there is a question how big of a win it is...
>
>
> [1] https://lore.kernel.org/all/20160620000606.GB3194@blaptop/
> [2] Google+ post RIP
Thanks for the feedback. (as I noted in other post), can A bit scanning
that detects hot VMA information be fed to NUMAB=1 scanning?
Regards
- Raghu
next prev parent reply other threads:[~2024-12-20 11:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 4:19 Slow-tier Page Promotion discussion recap and open questions 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 [this message]
2024-12-18 19:23 ` SeongJae Park
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=d72d37fb-03d8-45ed-8c4a-d18314049121@amd.com \
--to=rkodsara@amd.com \
--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=nadav.amit@gmail.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=santosh.shukla@amd.com \
--cc=shy828301@gmail.com \
--cc=sj@kernel.org \
--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