From: David Hildenbrand <david@redhat.com>
To: Zi Yan <ziy@nvidia.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] memory tiering: read last_cpupid correctly in do_huge_pmd_numa_page()
Date: Sat, 13 Jul 2024 03:23:00 +0200 [thread overview]
Message-ID: <f8d116fa-ae89-4d1e-a43f-79166c5d3075@redhat.com> (raw)
In-Reply-To: <65FBE843-2FEA-400B-9FFA-150E038F7BDA@nvidia.com>
On 13.07.24 03:18, Zi Yan wrote:
> On 12 Jul 2024, at 21:13, David Hildenbrand wrote:
>
>> On 12.07.24 04:44, Zi Yan wrote:
>>> From: Zi Yan <ziy@nvidia.com>
>>>
>>> last_cpupid is only available when memory tiering is off or the folio
>>> is in toptier node. Complete the check to read last_cpupid when it is
>>> available.
>>>
>>> Before the fix, the default last_cpupid will be used even if memory
>>> tiering mode is turned off at runtime instead of the actual value. This
>>> can prevent task_numa_fault() from getting right numa fault stats, but
>>> should not cause any crash. User might see performance changes after the
>>> fix.
>>>
>>> Fixes: 33024536bafd ("memory tiering: hot page selection with hint page fault latency")
>>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>>> ---
>>> mm/huge_memory.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>> index d7c84480f1a4..07d9dde4ca33 100644
>>> --- a/mm/huge_memory.c
>>> +++ b/mm/huge_memory.c
>>> @@ -1705,7 +1705,8 @@ vm_fault_t do_huge_pmd_numa_page(struct vm_fault *vmf)
>>> * For memory tiering mode, cpupid of slow memory page is used
>>> * to record page access time. So use default value.
>>> */
>>> - if (node_is_toptier(nid))
>>> + if (!(sysctl_numa_balancing_mode & NUMA_BALANCING_MEMORY_TIERING) ||
>>> + node_is_toptier(nid))
>>> last_cpupid = folio_last_cpupid(folio);
>>> target_nid = numa_migrate_prep(folio, vmf, haddr, nid, &flags);
>>> if (target_nid == NUMA_NO_NODE)
>>
>> Reported-by: ...
>
> Reported-by: David Hildenbrand <david@redhat.com>
>
> I suppose your email[1] reports the issue based on code inspection.
Yes, thanks for taking care of the fix and cleanups!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-07-13 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 2:44 [RFC PATCH 0/3] Fix and refactor do_{huge_pmd_}numa_page() Zi Yan
2024-07-12 2:44 ` [RFC PATCH 1/3] memory tiering: read last_cpupid correctly in do_huge_pmd_numa_page() Zi Yan
2024-07-12 3:22 ` Huang, Ying
2024-07-12 4:01 ` Baolin Wang
2024-07-13 1:13 ` David Hildenbrand
2024-07-13 1:18 ` Zi Yan
2024-07-13 1:23 ` David Hildenbrand [this message]
2024-07-12 2:44 ` [RFC PATCH 2/3] memory tiering: introduce folio_has_cpupid() check Zi Yan
2024-07-12 6:27 ` Huang, Ying
2024-07-12 2:44 ` [RFC PATCH 3/3] mm/migrate: move common code to numa_migrate_check (was numa_migrate_prep) Zi Yan
2024-07-18 8:36 ` Huang, Ying
2024-07-18 14:40 ` Zi Yan
2024-07-19 20:19 ` Zi Yan
2024-07-22 1:47 ` Huang, Ying
2024-07-22 14:01 ` Zi Yan
2024-07-22 15:21 ` Zi Yan
2024-07-23 1:16 ` Huang, Ying
2024-07-23 1:43 ` Zi Yan
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=f8d116fa-ae89-4d1e-a43f-79166c5d3075@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).