From: Bharata B Rao <bharata@amd.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
AneeshKumar.KizhakeVeetil@arm.com, Hasan.Maruf@amd.com,
Jonathan.Cameron@huawei.com, Michael.Day@amd.com,
akpm@linux-foundation.org, dave.hansen@intel.com,
david@redhat.com, feng.tang@intel.com, gourry@gourry.net,
hannes@cmpxchg.org, honggyu.kim@sk.com, hughd@google.com,
jhubbard@nvidia.com, k.shutemov@gmail.com, kbusch@meta.com,
kmanaouil.dev@gmail.com, leesuyeon0506@gmail.com,
leillc@google.com, liam.howlett@oracle.com,
mgorman@techsingularity.net, mingo@redhat.com,
nadav.amit@gmail.com, nphamcs@gmail.com, peterz@infradead.org,
raghavendra.kt@amd.com, riel@surriel.com, rientjes@google.com,
rppt@kernel.org, shivankg@amd.com, shy828301@gmail.com,
sj@kernel.org, vbabka@suse.cz, weixugc@google.com,
willy@infradead.org, ying.huang@linux.alibaba.com,
ziy@nvidia.com, yuanchu@google.com
Subject: Re: [RFC PATCH 2/4] mm: kpromoted: Hot page info collection and promotion daemon
Date: Mon, 17 Mar 2025 09:09:18 +0530 [thread overview]
Message-ID: <b9965654-af90-42c9-8e4b-b29621d11ea7@amd.com> (raw)
In-Reply-To: <20250313164430.bzkfyqmx6a5dj7d2@offworld>
On 13-Mar-25 10:14 PM, Davidlohr Bueso wrote:
> On Thu, 06 Mar 2025, Bharata B Rao wrote:
>
>> +static int page_should_be_promoted(struct page_hotness_info *phi)
>> +{
>> + struct page *page = pfn_to_online_page(phi->pfn);
>> + unsigned long now = jiffies;
>> + struct folio *folio;
>> +
>> + if (!page || is_zone_device_page(page))
>> + return false;
>> +
>> + folio = page_folio(page);
>> + if (!folio_test_lru(folio)) {
>> + count_vm_event(KPROMOTED_MIG_NON_LRU);
>> + return false;
>> + }
>> + if (folio_nid(folio) == phi->hot_node) {
>> + count_vm_event(KPROMOTED_MIG_RIGHT_NODE);
>> + return false;
>> + }
>
> How about using the LRU age itself:
Sounds like a good check for page hotness.
>
> if (folio_test_active())
> return true;
But the numbers I obtained with this check added, didn't really hit this
condition all that much. I was running a multi-threaded application that
allocates enough memory such that the allocation spills over from DRAM
node to the CXL node. Threads keep touching the memory pages in random
order.
kpromoted_recorded_accesses 960620 /* Number of recorded accesses */
kpromoted_recorded_hwhints 960620 /* Nr accesses via HW hints, IBS in
this case */
kpromoted_recorded_pgtscans 0
kpromoted_record_toptier 638006 /* Nr toptier accesses */
kpromoted_record_added 321234 /* Nr (CXL) accesses that are tracked */
kpromoted_record_exists 1380
kpromoted_mig_right_node 0
kpromoted_mig_non_lru 226
kpromoted_mig_lru_active 47 /* Number of accesses considered for
promotion as determined by folio_test_active() check */
kpromoted_mig_cold_old 0
kpromoted_mig_cold_not_accessed 1373
kpromoted_mig_candidate 319635
kpromoted_mig_promoted 319635
kpromoted_mig_dropped 1599
Need to check why is this the case.
>
>> +
>> + /* If the page was hot a while ago, don't promote */
>> + if ((now - phi->last_update) > 2 *
>> msecs_to_jiffies(KPROMOTED_FREQ_WINDOW)) {
>> + count_vm_event(KPROMOTED_MIG_COLD_OLD);
>> + return false;
>> + }
>> +
>> + /* If the page hasn't been accessed enough number of times, don't
>> promote */
>> + if (phi->frequency < KPRMOTED_FREQ_THRESHOLD) {
>> + count_vm_event(KPROMOTED_MIG_COLD_NOT_ACCESSED);
>> + return false;
>> + }
>> + return true;
>> +}
>
> ...
>
>> +static int kpromoted(void *p)
>> +{
>> + pg_data_t *pgdat = (pg_data_t *)p;
>> + struct task_struct *tsk = current;
>> + long timeout = msecs_to_jiffies(KPROMOTE_DELAY);
>> +
>> + const struct cpumask *cpumask = cpumask_of_node(pgdat->node_id);
>> +
>> + if (!cpumask_empty(cpumask))
>> + set_cpus_allowed_ptr(tsk, cpumask);
>
> Explicit cpumasks are not needed if you use kthread_create_on_node().
Thanks, will incorporate.
Regards,
Bharata.
next prev parent reply other threads:[~2025-03-17 3:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 5:45 [RFC PATCH 0/4] Kernel daemon for detecting and promoting hot pages Bharata B Rao
2025-03-06 5:45 ` [RFC PATCH 1/4] mm: migrate: Allow misplaced migration without VMA too Bharata B Rao
2025-03-06 12:13 ` David Hildenbrand
2025-03-07 3:00 ` Bharata B Rao
2025-03-06 17:24 ` Gregory Price
2025-03-06 17:45 ` Matthew Wilcox
2025-03-06 18:19 ` Gregory Price
2025-03-06 18:42 ` Matthew Wilcox
2025-03-06 20:03 ` Gregory Price
2025-03-24 2:55 ` Balbir Singh
2025-03-24 14:51 ` Bharata B Rao
2025-03-06 5:45 ` [RFC PATCH 2/4] mm: kpromoted: Hot page info collection and promotion daemon Bharata B Rao
2025-03-06 17:22 ` Mike Day
2025-03-07 3:27 ` Bharata B Rao
2025-03-13 16:44 ` Davidlohr Bueso
2025-03-17 3:39 ` Bharata B Rao [this message]
2025-03-17 15:05 ` Gregory Price
2025-03-17 16:22 ` Bharata B Rao
2025-03-17 18:24 ` Gregory Price
2025-03-13 20:36 ` Davidlohr Bueso
2025-03-17 3:49 ` Bharata B Rao
2025-03-14 15:28 ` Jonathan Cameron
2025-03-18 4:09 ` Bharata B Rao
2025-03-18 14:17 ` Jonathan Cameron
2025-03-24 3:35 ` Balbir Singh
2025-03-28 4:55 ` Bharata B Rao
2025-03-24 13:43 ` Gregory Price
2025-03-24 14:34 ` Bharata B Rao
2025-03-06 5:45 ` [RFC PATCH 3/4] x86: ibs: In-kernel IBS driver for memory access profiling Bharata B Rao
2025-03-14 15:38 ` Jonathan Cameron
2025-03-06 5:45 ` [RFC PATCH 4/4] x86: ibs: Enable IBS profiling for memory accesses Bharata B Rao
2025-03-16 22:00 ` [RFC PATCH 0/4] Kernel daemon for detecting and promoting hot pages SeongJae Park
2025-03-18 6:33 ` Raghavendra K T
2025-03-18 10:45 ` Bharata B Rao
2025-03-18 5:28 ` Balbir Singh
2025-03-20 9:07 ` Bharata B Rao
2025-03-21 6:19 ` Balbir Singh
2025-03-25 8:18 ` Bharata B Rao
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=b9965654-af90-42c9-8e4b-b29621d11ea7@amd.com \
--to=bharata@amd.com \
--cc=AneeshKumar.KizhakeVeetil@arm.com \
--cc=Hasan.Maruf@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Day@amd.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=feng.tang@intel.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=honggyu.kim@sk.com \
--cc=hughd@google.com \
--cc=jhubbard@nvidia.com \
--cc=k.shutemov@gmail.com \
--cc=kbusch@meta.com \
--cc=kmanaouil.dev@gmail.com \
--cc=leesuyeon0506@gmail.com \
--cc=leillc@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=nphamcs@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=shivankg@amd.com \
--cc=shy828301@gmail.com \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=yuanchu@google.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