From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) (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 40mz2x18RlzDr4q for ; Fri, 18 May 2018 03:35:05 +1000 (AEST) Subject: Re: [PATCH v11 01/26] mm: introduce CONFIG_SPECULATIVE_PAGE_FAULT To: Matthew Wilcox Cc: Laurent Dufour , akpm@linux-foundation.org, mhocko@kernel.org, peterz@infradead.org, kirill@shutemov.name, ak@linux.intel.com, dave@stgolabs.net, jack@suse.cz, khandual@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.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 , Jerome Glisse , Ganesh Mahendran , Minchan Kim , Punit Agrawal , vinayak menon , Yang Shi , linux-kernel@vger.kernel.org, linux-mm@kvack.org, haren@linux.vnet.ibm.com, npiggin@gmail.com, bsingharora@gmail.com, paulmck@linux.vnet.ibm.com, Tim Chen , linuxppc-dev@lists.ozlabs.org, x86@kernel.org References: <1526555193-7242-1-git-send-email-ldufour@linux.vnet.ibm.com> <1526555193-7242-2-git-send-email-ldufour@linux.vnet.ibm.com> <2cb8256d-5822-d94d-b0e6-c46f21d84852@infradead.org> <20180517171951.GB26718@bombadil.infradead.org> From: Randy Dunlap Message-ID: Date: Thu, 17 May 2018 10:34:53 -0700 MIME-Version: 1.0 In-Reply-To: <20180517171951.GB26718@bombadil.infradead.org> Content-Type: text/plain; charset=utf-8 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 05/17/2018 10:19 AM, Matthew Wilcox wrote: > On Thu, May 17, 2018 at 09:36:00AM -0700, Randy Dunlap wrote: >>> + If the speculative page fault fails because of a concurrency is >> >> because a concurrency is > > While one can use concurrency as a noun, it sounds archaic to me. I'd > rather: > > If the speculative page fault fails because a concurrent modification > is detected or because underlying PMD or PTE tables are not yet Yeah, OK. >>> + detected or because underlying PMD or PTE tables are not yet >>> + allocating, it is failing its processing and a classic page fault >> >> allocated, the speculative page fault fails and a classic page fault >> >>> + is then tried. -- ~Randy