From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, paulus@samba.org, linux-mm@kvack.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [RFC PATCH 0/9] powerpc: mm: Numa faults support for ppc64
Date: Tue, 22 Oct 2013 16:58:11 +0530 [thread overview]
Message-ID: <1382441300-1513-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com> (raw)
Hi,
This patch series add support for numa faults on ppc64 architecture. We steal the
_PAGE_COHERENCE bit and use that for indicating _PAGE_NUMA. We clear the _PAGE_PRESENT bit
and also invalidate the hpte entry on setting _PAGE_NUMA. The next fault on that
page will be considered a numa fault.
NOTE:
______
Issue:
I am finding large lock contention on page_table_lock with this series on a 95 cpu 4 node box with autonuma benchmark
I will out on vacation till NOV 6 without email access. Hence i will not be able to respond to review feedbacks
till then.
lock_stat version 0.3
-------------------------------------------------------------------------------------------------------------------------------------------------------
class name con-bounces contentions waittime-min waittime-max waittime-total acq-bounces acquisitions holdtime-mi hold time hold total
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
&(&mm->page_table_lock)->rlock: 713531791 719610919 0.09 3038193.19 357867523236.3 729709189 750040162 0.0 236991.36 1159646899.68
------------------------------
&(&mm->page_table_lock)->rlock 1 [<c000000000218880>] .anon_vma_prepare+0xb0/0x1e0
&(&mm->page_table_lock)->rlock 93 [<c000000000207ebc>] .do_numa_page+0x4c/0x190
&(&mm->page_table_lock)->rlock 301678 [<c0000000002139d4>] .change_protection+0x1d4/0x560
&(&mm->page_table_lock)->rlock 244524 [<c000000000213be8>] .change_protection+0x3e8/0x560
------------------------------
&(&mm->page_table_lock)->rlock 1 [<c000000000206a38>] .__do_fault+0x198/0x6b0
&(&mm->page_table_lock)->rlock 704163 [<c0000000002139d4>] .change_protection+0x1d4/0x560
&(&mm->page_table_lock)->rlock 207227 [<c000000000213be8>] .change_protection+0x3e8/0x560
&(&mm->page_table_lock)->rlock 95 [<c000000000207ebc>] .do_numa_page+0x4c/0x190
-aneesh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2013-10-22 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 11:28 Aneesh Kumar K.V [this message]
2013-10-22 11:28 ` [RFC PATCH 1/9] powerpc: Use HPTE constants when updating hpte bits Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 2/9] powerpc: Free up _PAGE_COHERENCE for numa fault use later Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 3/9] mm: Move change_prot_numa outside CONFIG_ARCH_USES_NUMA_PROT_NONE Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 4/9] powerpc: mm: Only check for _PAGE_PRESENT in set_pte/pmd functions Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 5/9] powerpc: mm: book3s: Enable _PAGE_NUMA for book3s Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 6/9] powerpc: mm: book3s: Disable hugepaged pmd format " Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 7/9] mm: numafaults: Use change_pmd_protnuma for updating _PAGE_NUMA for regular pmds Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 8/9] powerpc: mm: Support setting _PAGE_NUMA bit on pmd entry which are pointer to PTE page Aneesh Kumar K.V
2013-10-22 11:28 ` [RFC PATCH 9/9] powerpc: mm: Enable numa faulting for hugepages Aneesh Kumar K.V
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=1382441300-1513-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
/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).