fix numa vs kvm scalability issue
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | sched,numa: add cond_resched to task_numa_workkernel/ | +2 | 0 replies | |
| 2/3 | mm,numa: reorganize change_pmd_rangemm/ | +4 | 1 reply | |
| 3/3 | move mmu notifier call from change_protection to change_pmd_rangemm/ | +16 | 3 replies |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Chegu Vinod | David Rientjes |
|---|---|---|
| 1/3 | T-b | |
| 2/3 | T-b | A-b |
| 3/3 | T-b | A-b A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH -mm 0/3] fix numa vs kvm scalability issue
The NUMA scanning code can end up iterating over many gigabytes of unpopulated memory, especially in the case of a freshly started KVM guest with lots of memory.
This results in the mmu notifier code being called even when there are no mapped pages in a virtual address range. The amount of time wasted can be enough to trigger soft lockup warnings with very large (>2TB) KVM guests.
This patch moves the mmu notifier call to the pmd level, which represents 1GB areas of memory on x86-64. Furthermore, the mmu notifier code is only called from the address in the PMD where present mappings are first encountered.
The hugetlbfs code is left alone for now; hugetlb mappings are not relocatable, and as such are left alone by the NUMA code, and should never trigger this problem to begin with.
The series also adds a cond_resched to task_numa_work, to fix another potential latency issue.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>