From: "Huang, Ying" <ying.huang@intel.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Zi Yan <ziy@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
David Hildenbrand <david@redhat.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled.
Date: Tue, 23 Jul 2024 13:46:24 +0800 [thread overview]
Message-ID: <87wmlcek3z.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <d31b0226-6013-4152-af4b-1526146eb179@huawei.com> (Kefeng Wang's message of "Tue, 23 Jul 2024 11:24:23 +0800")
Kefeng Wang <wangkefeng.wang@huawei.com> writes:
> On 2024/7/23 9:54, Zi Yan wrote:
>> On Mon Jul 22, 2024 at 9:48 PM EDT, Kefeng Wang wrote:
>>>
>>>
>>> On 2024/7/23 1:29, Zi Yan wrote:
>>>> memory tiering can be enabled/disabled at runtime and
>>>> sysctl_numa_balancing_mode & NUMA_BALANCING_MEMORY_TIERING is used to check
>>>> it. In migrate_misplaced_folio(), the check is missing when
>>>> PGPROMOTE_SUCCESS is incremented. Add the missing check.
>>>>
>>>> Reported-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>>>> Closes: https://lore.kernel.org/linux-mm/f4ae2c9c-fe40-4807-bdb2-64cf2d716c1a@huawei.com/
>>>> Fixes: 33024536bafd ("memory tiering: hot page selection with hint page fault latency")
>>>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>>>
>>> Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>>>
>> Thanks.
>>
>>>> ---
>>>> mm/migrate.c | 4 +++-
>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/mm/migrate.c b/mm/migrate.c
>>>> index bdbb5bb04c91..b819809da470 100644
>>>> --- a/mm/migrate.c
>>>> +++ b/mm/migrate.c
>>>> @@ -2630,7 +2630,9 @@ int migrate_misplaced_folio(struct folio *folio, struct vm_area_struct *vma,
>>>> putback_movable_pages(&migratepages);
>>>> if (nr_succeeded) {
>>>> count_vm_numa_events(NUMA_PAGE_MIGRATE, nr_succeeded);
>>>> - if (!node_is_toptier(folio_nid(folio)) && node_is_toptier(node))
>>>> + if ((sysctl_numa_balancing_mode & NUMA_BALANCING_MEMORY_TIERING)
>>>> + && !node_is_toptier(folio_nid(folio))
>>>> + && node_is_toptier(node))
>>>> mod_node_page_state(pgdat, PGPROMOTE_SUCCESS,
>>>> nr_succeeded);
>>>
>>> The should be in advance of patch2, and change above to use
>>> folio_has_cpupid() helper() too.
>> It shares the same logic of !folio_has_cpupid() but it might be
>> confusing to
>> put !folio_has_cpupid(folio) && node_is_toptier(node) here. folio's
>> cpupid has nothing to do with the stats here, thus I did not use the
>> function.
>
> If folio don't include access time, we do migrate it but it isn't a
> promotion, so don't count it, other comments?
Personally, I prefer to use !node_is_toptier() && node_is_toptier()
here. That sounds more natural for me.
> PS: Could we rename folio_has_cpupid() to folio_has_access_time(),
> even without memory_tiering, we still have cpupid in folio, right?
--
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2024-07-23 5:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 17:29 [PATCH v2 1/3] memory tiering: read last_cpupid correctly in do_huge_pmd_numa_page() Zi Yan
2024-07-22 17:29 ` [PATCH v2 2/3] memory tiering: introduce folio_has_cpupid() check Zi Yan
2024-07-23 5:54 ` Lorenzo Stoakes
2024-07-23 10:14 ` David Hildenbrand
2024-07-23 12:55 ` Zi Yan
2024-07-22 17:29 ` [PATCH v2 3/3] memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled Zi Yan
2024-07-23 1:48 ` Kefeng Wang
2024-07-23 1:54 ` Zi Yan
2024-07-23 3:24 ` Kefeng Wang
2024-07-23 5:46 ` Huang, Ying [this message]
2024-07-23 10:17 ` David Hildenbrand
2024-07-23 13:03 ` Zi Yan
2024-07-24 1:22 ` Kefeng Wang
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=87wmlcek3z.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangkefeng.wang@huawei.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