From patchwork Mon Oct 9 10:07:32 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Laurent Dufour X-Patchwork-Id: 823159 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3y9bbH43mcz9tXx for ; Mon, 9 Oct 2017 21:10:19 +1100 (AEDT) Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 3y9bbH3D4RzDr5C for ; Mon, 9 Oct 2017 21:10:19 +1100 (AEDT) X-Original-To: linuxppc-dev@lists.ozlabs.org Delivered-To: linuxppc-dev@lists.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=linux.vnet.ibm.com (client-ip=148.163.156.1; helo=mx0a-001b2d01.pphosted.com; envelope-from=ldufour@linux.vnet.ibm.com; receiver=) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3y9bXl3xgzzDqlv for ; Mon, 9 Oct 2017 21:08:07 +1100 (AEDT) Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v99A4osg056747 for ; Mon, 9 Oct 2017 06:08:05 -0400 Received: from e06smtp10.uk.ibm.com (e06smtp10.uk.ibm.com [195.75.94.106]) by mx0a-001b2d01.pphosted.com with ESMTP id 2dg5xwk7yv-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 09 Oct 2017 06:08:05 -0400 Received: from localhost by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 9 Oct 2017 11:08:01 +0100 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) by e06smtp10.uk.ibm.com (192.168.101.140) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 9 Oct 2017 11:07:55 +0100 Received: from d06av21.portsmouth.uk.ibm.com (d06av21.portsmouth.uk.ibm.com [9.149.105.232]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v99A7sDj25100522; Mon, 9 Oct 2017 10:07:54 GMT Received: from d06av21.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 44CF752043; Mon, 9 Oct 2017 10:02:27 +0100 (BST) Received: from nimbus.lab.toulouse-stg.fr.ibm.com (unknown [9.145.51.101]) by d06av21.portsmouth.uk.ibm.com (Postfix) with ESMTP id 831ED5203F; Mon, 9 Oct 2017 10:02:25 +0100 (BST) From: Laurent Dufour To: paulmck@linux.vnet.ibm.com, peterz@infradead.org, akpm@linux-foundation.org, kirill@shutemov.name, ak@linux.intel.com, mhocko@kernel.org, dave@stgolabs.net, jack@suse.cz, Matthew Wilcox , benh@kernel.crashing.org, mpe@ellerman.id.au, paulus@samba.org, Thomas Gleixner , Ingo Molnar , hpa@zytor.com, Will Deacon , Sergey Senozhatsky , Andrea Arcangeli , Alexei Starovoitov Subject: [PATCH v4 00/20] Speculative page faults Date: Mon, 9 Oct 2017 12:07:32 +0200 X-Mailer: git-send-email 2.7.4 X-TM-AS-GCONF: 00 x-cbid: 17100910-0040-0000-0000-000003E0C559 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17100910-0041-0000-0000-000025E24182 Message-Id: <1507543672-25821-1-git-send-email-ldufour@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-09_02:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710090147 X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.24 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linuxppc-dev@lists.ozlabs.org, x86@kernel.org, linux-kernel@vger.kernel.org, npiggin@gmail.com, linux-mm@kvack.org, Tim Chen , haren@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com Errors-To: linuxppc-dev-bounces+patchwork-incoming=ozlabs.org@lists.ozlabs.org Sender: "Linuxppc-dev" This is a port on kernel 4.14 of the work done by Peter Zijlstra to handle page fault without holding the mm semaphore [1]. The idea is to try to handle user space page faults without holding the mmap_sem. This should allow better concurrency for massively threaded process since the page fault handler will not wait for other threads memory layout change to be done, assuming that this change is done in another part of the process's memory space. This type page fault is named speculative page fault. If the speculative page fault fails because of a concurrency is detected or because underlying PMD or PTE tables are not yet allocating, it is failing its processing and a classic page fault is then tried. The speculative page fault (SPF) has to look for the VMA matching the fault address without holding the mmap_sem, so the VMA list is now managed using SRCU allowing lockless walking. The only impact would be the deferred file derefencing in the case of a file mapping, since the file pointer is released once the SRCU cleaning is done. This patch relies on the change done recently by Paul McKenney in SRCU which now runs a callback per CPU instead of per SRCU structure [1]. The VMA's attributes checked during the speculative page fault processing have to be protected against parallel changes. This is done by using a per VMA sequence lock. This sequence lock allows the speculative page fault handler to fast check for parallel changes in progress and to abort the speculative page fault in that case. Once the VMA is found, the speculative page fault handler would check for the VMA's attributes to verify that the page fault has to be handled correctly or not. Thus the VMA is protected through a sequence lock which allows fast detection of concurrent VMA changes. If such a change is detected, the speculative page fault is aborted and a *classic* page fault is tried. VMA sequence locks are added when VMA attributes which are checked during the page fault are modified. When the PTE is fetched, the VMA is checked to see if it has been changed, so once the page table is locked, the VMA is valid, so any other changes leading to touching this PTE will need to lock the page table, so no parallel change is possible at this time. Compared to the Peter's initial work, this series introduces a spin_trylock when dealing with speculative page fault. This is required to avoid dead lock when handling a page fault while a TLB invalidate is requested by an other CPU holding the PTE. Another change due to a lock dependency issue with mapping->i_mmap_rwsem. In addition some VMA field values which are used once the PTE is unlocked at the end the page fault path are saved into the vm_fault structure to used the values matching the VMA at the time the PTE was locked. This series only support VMA with no vm_ops define, so huge page and mapped file are not managed with the speculative path. In addition transparent huge page are not supported. Once this series will be accepted upstream I'll extend the support to mapped files, and transparent huge pages. This series builds on top of v4.14-rc3-mmotm and is functional on x86 and PowerPC. Tests have been made using a large commercial in-memory database on a PowerPC system with 752 CPU using RFC v5 using a previous version of this series. The results are very encouraging since the loading of the 2TB database was faster by 14% with the speculative page fault. Using ebizzy test [3], which spreads a lot of threads, the result are good when running on both a large or a small system. When using kernbench, the result are quite similar which expected as not so much multithreaded processes are involved. But there is no performance degradation neither which is good. ------------------ Benchmarks results Note there is no changes compared to the one recorded with the v3 series. Ebizzy: ------- The test is counting the number of records per second it can manage, the higher is the best. I run it like this 'ebizzy -mTRp'. To get consistent result I repeated the test 100 times and measure the average result, mean deviation, max and min. - 16 CPUs x86 VM 4.14.0-rc3-mm1 4.14.0-rc3-mm1-spf delta Records/s 14140,93 66325,09 +369.03% mean deviation 788,48 2910,02 +269.07% max 19820 77836 +292.71% min 12892 61987 +380.82% - 80 CPUs Power 8 node: 4.14.0-rc3-mm1 4.14.0-rc3-mm1-spf delta Records/s 34556,49 69156,08 +100.12% mean deviation 705,50 1767,88 +150.59% max 37423 76801 +105.22% min 32873 63524 +93.24% Kernbench: ---------- This test is building a 4.12 kernel using platform default config. The build has been run 5 times each time. - 16 CPUs x86 VM Average Half load -j 8 Run (std deviation) 4.14.0-rc3-mm1 4.14.0-rc3-mm1-spf delta Elapsed Time 143.292 (0.24407) 146.12 (0.548042) +1.97% User Time 995.582 (1.52229) 1005.22 (1.56144) +0.97% System Time 100.84 (0.645484) 111.666 (0.443091) +10.74% Percent CPU 764.6 (1.14018) 763.8 (1.78885) -0.10% Context Switches 47226.4 (981.585) 64360.2 (909.638) +36.28% Sleeps 85328 (766.874) 85254 (1079.3) -0.09% Average Optimal load -j 16 Run (std deviation): 4.14.0-rc3-mm1 4.14.0-rc3-mm1-spf delta Elapsed Time 73.548 (0.373323) 74.574 (0.737923) +1.40% User Time 950.151 (47.9032) 957.562 (50.2442) +0.78% System Time 93.522 (7.72959) 102.671 (9.48787) +9.78% Percent CPU 1055.7 (306.87) 1054.6 (306.657) -0.10% Context Switches 65758.7 (19550.8) 86997.8 (23875.9) +32.30% Sleeps 89873.3 (4839.81) 90715.5 (5807.7) +0.94% - 80 CPUs Power 8 node: Average Half load -j 8 Run (std deviation) 4.14.0-rc3-mm1 4.14.0-rc3-mm1-spf delta Elapsed Time 110.358 (0.555761) 110.702 (1.14049) +0.31% User Time 4161.09 (23.8605) 4161.2 (9.23829) +0.00% System Time 103.914 (0.553471) 105.446 (0.689732) +1.47% Percent CPU 3864.2 (15.975) 3853.8 (34.0764) -0.27% Context Switches 79463.8 (784.022) 80104 (337.843) +0.81% Sleeps 158318 (1314.63) 157907 (2207.88) -0.26% Average Optimal load -j 80 Run (std deviation): 4.14.0-rc3-mm1 4.14.0-rc3-mm1-spf delta Elapsed Time 99.056 (0.877001) 99.394 (0.815156) +0.34% User Time 5421.85 (1329.09) 5418.06 (1324.93) -0.07% System Time 117.709 (14.5563) 119.492 (14.8268) +1.51% Percent CPU 5371.4 (1589.31) 5351.8 (1579.95) -0.36% Context Switches 126178 (49246.1) 139214 (62310.5) +10.33% Sleeps 154194 (5668.38) 152706 (6659.51) -0.97% Impact on the text size for x86_64: UP SMP 4.14.0-rc3-mm1 0x008ed859 0x00966ea9 4.14.0-rc3-mm1-spf 0x008ed859 0x00968ea9 ------------------------ Changes since v3: - Don't build when CONFIG_SMP is not set - Fixed a lock dependency warning in __vma_adjust() - Use READ_ONCE to access p*d values in handle_speculative_fault() - Call memcp_oom() service in handle_speculative_fault() Changes since v2: - Perf event is renamed in PERF_COUNT_SW_SPF - On Power handle do_page_fault()'s cleaning - On Power if the VM_FAULT_ERROR is returned by handle_speculative_fault(), do not retry but jump to the error path - If VMA's flags are not matching the fault, directly returns VM_FAULT_SIGSEGV and not VM_FAULT_RETRY - Check for pud_trans_huge() to avoid speculative path - Handles _vm_normal_page()'s introduced by 6f16211df3bf ("mm/device-public-memory: device memory cache coherent with CPU") - add and review few comments in the code Changes since v1: - Remove PERF_COUNT_SW_SPF_FAILED perf event. - Add tracing events to details speculative page fault failures. - Cache VMA fields values which are used once the PTE is unlocked at the end of the page fault events. - Ensure that fields read during the speculative path are written and read using WRITE_ONCE and READ_ONCE. - Add checks at the beginning of the speculative path to abort it if the VMA is known to not be supported. Changes since RFC V5 [5] - Port to 4.13 kernel - Merging patch fixing lock dependency into the original patch - Replace the 2 parameters of vma_has_changed() with the vmf pointer - In patch 7, don't call __do_fault() in the speculative path as it may want to unlock the mmap_sem. - In patch 11-12, don't check for vma boundaries when page_add_new_anon_rmap() is called during the spf path and protect against anon_vma pointer's update. - In patch 13-16, add performance events to report number of successful and failed speculative events. [1] http://linux-kernel.2935.n7.nabble.com/RFC-PATCH-0-6-Another-go-at-speculative-page-faults-tt965642.html#none [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da915ad5cf25b5f5d358dd3670c3378d8ae8c03e [3] http://ebizzy.sourceforge.net/ [4] http://ck.kolivas.org/apps/kernbench/kernbench-0.50/ [5] https://lwn.net/Articles/725607/ Laurent Dufour (14): mm: Introduce pte_spinlock for FAULT_FLAG_SPECULATIVE mm: Protect VMA modifications using VMA sequence count mm: Cache some VMA fields in the vm_fault structure mm: Protect SPF handler against anon_vma changes mm/migrate: Pass vm_fault pointer to migrate_misplaced_page() mm: Introduce __lru_cache_add_active_or_unevictable mm: Introduce __maybe_mkwrite() mm: Introduce __vm_normal_page() mm: Introduce __page_add_new_anon_rmap() mm: Try spin lock in speculative path mm: Adding speculative page fault failure trace events perf: Add a speculative page fault sw event perf tools: Add support for the SPF perf event powerpc/mm: Add speculative page fault Peter Zijlstra (6): mm: Dont assume page-table invariance during faults mm: Prepare for FAULT_FLAG_SPECULATIVE mm: VMA sequence count mm: RCU free VMAs mm: Provide speculative fault infrastructure x86/mm: Add speculative pagefault handling arch/powerpc/include/asm/book3s/64/pgtable.h | 5 + arch/powerpc/mm/fault.c | 17 + arch/x86/include/asm/pgtable_types.h | 7 + arch/x86/mm/fault.c | 21 ++ fs/proc/task_mmu.c | 5 +- fs/userfaultfd.c | 17 +- include/linux/hugetlb_inline.h | 2 +- include/linux/migrate.h | 4 +- include/linux/mm.h | 69 +++- include/linux/mm_types.h | 5 + include/linux/pagemap.h | 4 +- include/linux/rmap.h | 12 +- include/linux/swap.h | 11 +- include/trace/events/pagefault.h | 87 +++++ include/uapi/linux/perf_event.h | 1 + kernel/fork.c | 1 + mm/hugetlb.c | 2 + mm/init-mm.c | 1 + mm/internal.h | 21 ++ mm/khugepaged.c | 5 + mm/madvise.c | 6 +- mm/memory.c | 496 +++++++++++++++++++++++---- mm/mempolicy.c | 51 ++- mm/migrate.c | 4 +- mm/mlock.c | 13 +- mm/mmap.c | 160 +++++++-- mm/mprotect.c | 4 +- mm/mremap.c | 6 + mm/rmap.c | 5 +- mm/swap.c | 12 +- tools/include/uapi/linux/perf_event.h | 1 + tools/perf/util/evsel.c | 1 + tools/perf/util/parse-events.c | 4 + tools/perf/util/parse-events.l | 1 + tools/perf/util/python.c | 1 + 35 files changed, 910 insertions(+), 152 deletions(-) create mode 100644 include/trace/events/pagefault.h