From: David Hildenbrand <david@redhat.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
Zi Yan <ziy@nvidia.com>,
linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Huang, Ying" <ying.huang@intel.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] mm/numa: no task_numa_fault() call if page table is changed
Date: Thu, 8 Aug 2024 10:22:50 +0200 [thread overview]
Message-ID: <1881267a-723d-4ba0-96d0-d863ae9345a4@redhat.com> (raw)
In-Reply-To: <956553dc-587c-4a43-9877-7e8844f27f95@linux.alibaba.com>
On 08.08.24 05:19, Baolin Wang wrote:
>
>
> On 2024/8/8 02:47, Zi Yan wrote:
>> When handling a numa page fault, task_numa_fault() should be called by a
>> process that restores the page table of the faulted folio to avoid
>> duplicated stats counting. Commit b99a342d4f11 ("NUMA balancing: reduce
>> TLB flush via delaying mapping on hint page fault") restructured
>> do_numa_page() and do_huge_pmd_numa_page() and did not avoid
>> task_numa_fault() call in the second page table check after a numa
>> migration failure. Fix it by making all !pte_same()/!pmd_same() return
>> immediately.
>>
>> This issue can cause task_numa_fault() being called more than necessary
>> and lead to unexpected numa balancing results (It is hard to tell whether
>> the issue will cause positive or negative performance impact due to
>> duplicated numa fault counting).
>>
>> Reported-by: "Huang, Ying" <ying.huang@intel.com>
>> Closes: https://lore.kernel.org/linux-mm/87zfqfw0yw.fsf@yhuang6-desk2.ccr.corp.intel.com/
>> Fixes: b99a342d4f11 ("NUMA balancing: reduce TLB flush via delaying mapping on hint page fault")
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>
> The fix looks reasonable to me. Feel free to add:
> Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>
> (Nit: These goto labels are a bit confusing and might need some cleanup
> in the future.)
Agreed, maybe we should simply handle that right away and replace the "goto out;" users by "return 0;".
Then, just copy the 3 LOC.
For mm/memory.c that would be:
diff --git a/mm/memory.c b/mm/memory.c
index 67496dc5064f..410ba50ca746 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -5461,7 +5461,7 @@ static vm_fault_t do_numa_page(struct vm_fault *vmf)
if (unlikely(!pte_same(old_pte, vmf->orig_pte))) {
pte_unmap_unlock(vmf->pte, vmf->ptl);
- goto out;
+ return 0;
}
pte = pte_modify(old_pte, vma->vm_page_prot);
@@ -5528,15 +5528,14 @@ static vm_fault_t do_numa_page(struct vm_fault *vmf)
vmf->pte = pte_offset_map_lock(vma->vm_mm, vmf->pmd,
vmf->address, &vmf->ptl);
if (unlikely(!vmf->pte))
- goto out;
+ return 0;
if (unlikely(!pte_same(ptep_get(vmf->pte), vmf->orig_pte))) {
pte_unmap_unlock(vmf->pte, vmf->ptl);
- goto out;
+ return 0;
}
goto out_map;
}
-out:
if (nid != NUMA_NO_NODE)
task_numa_fault(last_cpupid, nid, nr_pages, flags);
return 0;
@@ -5552,7 +5551,9 @@ static vm_fault_t do_numa_page(struct vm_fault *vmf)
numa_rebuild_single_mapping(vmf, vma, vmf->address, vmf->pte,
writable);
pte_unmap_unlock(vmf->pte, vmf->ptl);
- goto out;
+ if (nid != NUMA_NO_NODE)
+ task_numa_fault(last_cpupid, nid, nr_pages, flags);
+ return 0;
}
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-08-08 8:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 18:47 Zi Yan
2024-08-07 18:47 ` [PATCH 2/2] mm/migrate: move common code to numa_migrate_check (was numa_migrate_prep) Zi Yan
2024-08-08 4:14 ` Huang, Ying
2024-08-08 14:59 ` Zi Yan
2024-08-08 23:13 ` Zi Yan
2024-08-08 3:19 ` [PATCH 1/2] mm/numa: no task_numa_fault() call if page table is changed Baolin Wang
2024-08-08 8:22 ` David Hildenbrand [this message]
2024-08-08 9:25 ` Baolin Wang
2024-08-08 14:13 ` Zi Yan
2024-08-08 14:14 ` David Hildenbrand
2024-08-08 14:21 ` Zi Yan
2024-08-08 14:36 ` Kefeng Wang
2024-08-08 14:57 ` Zi Yan
2024-08-08 15:12 ` Zi Yan
2024-08-09 1:25 ` Huang, Ying
2024-08-09 2:05 ` Zi Yan
2024-08-09 7:52 ` Huang, Ying
2024-08-09 13:28 ` Zi Yan
2024-08-09 13:49 ` David Hildenbrand
2024-08-09 14:17 ` 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=1881267a-723d-4ba0-96d0-d863ae9345a4@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=stable@vger.kernel.org \
--cc=wangkefeng.wang@huawei.com \
--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
all inboxes | Powered by JetHome®