From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by kanga.kvack.org (Postfix) with ESMTP id E868D6B0037 for ; Tue, 11 Mar 2014 15:24:34 -0400 (EDT) Received: by mail-qa0-f49.google.com with SMTP id j7so1455772qaq.8 for ; Tue, 11 Mar 2014 12:24:34 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTP id o92si11736847qgd.107.2014.03.11.12.24.34 for ; Tue, 11 Mar 2014 12:24:34 -0700 (PDT) Message-ID: <531F48C2.6010408@redhat.com> Date: Tue, 11 Mar 2014 13:32:50 -0400 From: Rik van Riel MIME-Version: 1.0 Subject: Re: [PATCH -mm] mm,numa,mprotect: always continue after finding a stable thp page References: <5318E4BC.50301@oracle.com> <20140306173137.6a23a0b2@cuia.bos.redhat.com> <5318FC3F.4080204@redhat.com> <20140307140650.GA1931@suse.de> <20140307150923.GB1931@suse.de> <20140307182745.GD1931@suse.de> <20140311162845.GA30604@suse.de> <531F3F15.8050206@oracle.com> <531F4128.8020109@redhat.com> <531F48CC.303@oracle.com> In-Reply-To: <531F48CC.303@oracle.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Sasha Levin , Mel Gorman Cc: David Rientjes , Andrew Morton , "linux-mm@kvack.org" , LKML , hhuang@redhat.com, knoel@redhat.com, aarcange@redhat.com On 03/11/2014 01:33 PM, Sasha Levin wrote: > On 03/11/2014 01:00 PM, Rik van Riel wrote: >> On 03/11/2014 12:51 PM, Sasha Levin wrote: >>> On 03/11/2014 12:28 PM, Mel Gorman wrote: >>>> On Fri, Mar 07, 2014 at 06:27:45PM +0000, Mel Gorman wrote: >>>>>> This is a completely untested prototype. It rechecks pmd_trans_huge >>>>>> under the lock and falls through if it hit a parallel split. It's not >>>>>> perfect because it could decide to fall through just because there >>>>>> was >>>>>> no prot_numa work to do but it's for illustration purposes. Secondly, >>>>>> I noted that you are calling invalidate for every pmd range. Is that >>>>>> not >>>>>> a lot of invalidations? We could do the same by just tracking the >>>>>> address >>>>>> of the first invalidation. >>>>>> >>>>> >>>>> And there were other minor issues. This is still untested but Sasha, >>>>> can you try it out please? I discussed this with Rik on IRC for a bit >>>>> and >>>>> reckon this should be sufficient if the correct race has been >>>>> identified. >>>>> >>>> >>>> Any luck with this patch Sasha? It passed basic tests here but I had >>>> not >>>> seen the issue trigger either. >>>> >>> >>> Sorry, I've been stuck in my weekend project of getting lockdep to work >>> with page locks :) >>> >>> It takes a moment to test, so just to be sure - I should have only this >>> last patch applied? >>> Without the one in the original mail? >> >> Indeed, only this patch should do it. > > Okay. So just this patch on top of the latest -next shows the following > issues: OK, those are all issues with Davidlohr Bueso's per-thread vma cache patch :) -- 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: email@kvack.org