Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3711981yba; Tue, 23 Apr 2019 08:23:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqxpvhK+dI/gkYd4F3KXO40gQdzaIkhVIilrJP3FMKb6y8e/na5Uc0C91U4fqdmKNFmVgtB7 X-Received: by 2002:a62:5ec2:: with SMTP id s185mr28216307pfb.16.1556033018167; Tue, 23 Apr 2019 08:23:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556033018; cv=none; d=google.com; s=arc-20160816; b=GAn6cASDVfUuc/vzjJpDrJlHxEJUDOElbIR+O9cFO/ygBkTpQjCWjgmAnxMT61WB7i s7IusziIyS3bNROKo6Hgxg66o0i2Vy50cBazFdXzWtOFiRnA/fu4oezpV55TIshZuoRo 4xuQ25Uh14CTkbjYG3h/B8WYi+rlsOT1LJPU78P2O0PcfVuroBOXGccqPXqcwWwSLAvw HSf3rptQ8RVT0qOY3FA6JvauAbjnN5Ugbt0a9AThP2FbGEHXPAtWuoxKJKD4P/k6dPis YuYp2DwskIgr3gv1al7rwI2Jdezw741DnE/ycGLEck+zqY1DrfzW723kJrQlu/7+ohcA oQBA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:cc:to:subject; bh=1Hq9GDwpavLHPlAi4sgV7BnTVf/FARNXWXz3UrUgYK4=; b=ghKm2Vm3RVrOYXVXjtFjXiv1r4Yz+q6UP652uHuJA7dL4vgMEeC7g6q33ynOckHmw/ zsPTl0ugFVI52LlDYxH8eOEJm8Sf2TVRWTLREdQv5/ESD4AgQj2SBWD68FGjTO75jgg+ udvU7Z6r3GWjTnWGTT7NrmHZES9t9I9bcsRqj8u74F5qwIXYr/Tee8vvXrQ3LcKl4x3N fT3G4ElOAQS4MAJKicMumdOqAE6OKp6jsR870JFwUSp2j+v8Nqac8wbgejKKBsItQxNO hC8GwPrcwBwbrXgaPx2Sm9I4YibesoDZDBYr4/ZSeUf5gFD8F9X92o9lcW5Nj6yEom/n a9BQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z2si16871836pfz.143.2019.04.23.08.23.22; Tue, 23 Apr 2019 08:23:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728385AbfDWPWE (ORCPT + 99 others); Tue, 23 Apr 2019 11:22:04 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:46436 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727745AbfDWPWE (ORCPT ); Tue, 23 Apr 2019 11:22:04 -0400 Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3NFKeoB043492 for ; Tue, 23 Apr 2019 11:22:02 -0400 Received: from e06smtp03.uk.ibm.com (e06smtp03.uk.ibm.com [195.75.94.99]) by mx0a-001b2d01.pphosted.com with ESMTP id 2s242uuy6c-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 23 Apr 2019 11:22:01 -0400 Received: from localhost by e06smtp03.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 23 Apr 2019 16:21:52 +0100 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp03.uk.ibm.com (192.168.101.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 23 Apr 2019 16:21:42 +0100 Received: from d06av24.portsmouth.uk.ibm.com (mk.ibm.com [9.149.105.60]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x3NFLfkJ26017998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 23 Apr 2019 15:21:41 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DC7BC42045; Tue, 23 Apr 2019 15:21:40 +0000 (GMT) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 678A04204D; Tue, 23 Apr 2019 15:21:38 +0000 (GMT) Received: from [9.145.7.116] (unknown [9.145.7.116]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 23 Apr 2019 15:21:38 +0000 (GMT) Subject: Re: [PATCH v12 01/31] mm: introduce CONFIG_SPECULATIVE_PAGE_FAULT To: Jerome Glisse Cc: akpm@linux-foundation.org, mhocko@kernel.org, peterz@infradead.org, kirill@shutemov.name, ak@linux.intel.com, dave@stgolabs.net, jack@suse.cz, Matthew Wilcox , aneesh.kumar@linux.ibm.com, benh@kernel.crashing.org, mpe@ellerman.id.au, paulus@samba.org, Thomas Gleixner , Ingo Molnar , hpa@zytor.com, Will Deacon , Sergey Senozhatsky , sergey.senozhatsky.work@gmail.com, Andrea Arcangeli , Alexei Starovoitov , kemi.wang@intel.com, Daniel Jordan , David Rientjes , Ganesh Mahendran , Minchan Kim , Punit Agrawal , vinayak menon , Yang Shi , zhong jiang , Haiyan Song , Balbir Singh , sj38.park@gmail.com, Michel Lespinasse , Mike Rapoport , linux-kernel@vger.kernel.org, linux-mm@kvack.org, haren@linux.vnet.ibm.com, npiggin@gmail.com, paulmck@linux.vnet.ibm.com, Tim Chen , linuxppc-dev@lists.ozlabs.org, x86@kernel.org References: <20190416134522.17540-1-ldufour@linux.ibm.com> <20190416134522.17540-2-ldufour@linux.ibm.com> <20190418214721.GA11645@redhat.com> From: Laurent Dufour Date: Tue, 23 Apr 2019 17:21:37 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190418214721.GA11645@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 19042315-0012-0000-0000-00000311DE1E X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19042315-0013-0000-0000-0000214A2FD2 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-04-23_04:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904230103 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 18/04/2019 à 23:47, Jerome Glisse a écrit : > On Tue, Apr 16, 2019 at 03:44:52PM +0200, Laurent Dufour wrote: >> This configuration variable will be used to build the code needed to >> handle speculative page fault. >> >> By default it is turned off, and activated depending on architecture >> support, ARCH_HAS_PTE_SPECIAL, SMP and MMU. >> >> The architecture support is needed since the speculative page fault handler >> is called from the architecture's page faulting code, and some code has to >> be added there to handle the speculative handler. >> >> The dependency on ARCH_HAS_PTE_SPECIAL is required because vm_normal_page() >> does processing that is not compatible with the speculative handling in the >> case ARCH_HAS_PTE_SPECIAL is not set. >> >> Suggested-by: Thomas Gleixner >> Suggested-by: David Rientjes >> Signed-off-by: Laurent Dufour > > Reviewed-by: Jérôme Glisse Thanks Jérôme. > Small question below > >> --- >> mm/Kconfig | 22 ++++++++++++++++++++++ >> 1 file changed, 22 insertions(+) >> >> diff --git a/mm/Kconfig b/mm/Kconfig >> index 0eada3f818fa..ff278ac9978a 100644 >> --- a/mm/Kconfig >> +++ b/mm/Kconfig >> @@ -761,4 +761,26 @@ config GUP_BENCHMARK >> config ARCH_HAS_PTE_SPECIAL >> bool >> >> +config ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT >> + def_bool n >> + >> +config SPECULATIVE_PAGE_FAULT >> + bool "Speculative page faults" >> + default y >> + depends on ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT >> + depends on ARCH_HAS_PTE_SPECIAL && MMU && SMP >> + help >> + Try to handle user space page faults without holding the mmap_sem. >> + >> + This should allow better concurrency for massively threaded processes > > Is there any case where it does not provide better concurrency ? The > should make me wonder :) Depending on the VMA's type, it may not provide better concurrency. Indeed only anonymous mapping are managed currently. Perhaps this should be mentioned here, is it ? >> + since the page fault handler will not wait for other thread's memory >> + layout change to be done, assuming that this change is done in >> + another part of the process's memory space. This type of page fault >> + is named speculative page fault. >> + >> + If the speculative page fault fails because a concurrent modification >> + is detected or because underlying PMD or PTE tables are not yet >> + allocated, the speculative page fault fails and a classic page fault >> + is then tried. >> + >> endmenu >> -- >> 2.21.0 >> >