From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) by kanga.kvack.org (Postfix) with ESMTP id 2ABC68E0073 for ; Thu, 24 Jan 2019 02:05:14 -0500 (EST) Received: by mail-qt1-f198.google.com with SMTP id n39so5478708qtn.18 for ; Wed, 23 Jan 2019 23:05:14 -0800 (PST) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTPS id k8si418537qvp.96.2019.01.23.23.05.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jan 2019 23:05:13 -0800 (PST) Date: Thu, 24 Jan 2019 15:05:03 +0800 From: Peter Xu Subject: Re: [PATCH RFC 04/24] mm: gup: allow VM_FAULT_RETRY for multiple times Message-ID: <20190124070503.GJ18231@xz-x1> References: <20190121075722.7945-1-peterx@redhat.com> <20190121075722.7945-5-peterx@redhat.com> <20190121162455.GC3711@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190121162455.GC3711@redhat.com> Sender: owner-linux-mm@kvack.org List-ID: To: Jerome Glisse Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Hugh Dickins , Maya Gokhale , Johannes Weiner , Martin Cracauer , Denis Plotnikov , Shaohua Li , Andrea Arcangeli , Mike Kravetz , Marty McFadden , Mike Rapoport , Mel Gorman , "Kirill A . Shutemov" , "Dr . David Alan Gilbert" On Mon, Jan 21, 2019 at 11:24:55AM -0500, Jerome Glisse wrote: > On Mon, Jan 21, 2019 at 03:57:02PM +0800, Peter Xu wrote: > > This is the gup counterpart of the change that allows the VM_FAULT_RETRY > > to happen for more than once. > > > > Signed-off-by: Peter Xu > > So it would be nice to add a comment in the code and in the commit message > about possible fault starvation (mostly due to previous patch changes) as > if some one experience that and try to bisect it might overlook the commit. > > Otherwise: > > Reviewed-by: Jérôme Glisse Jerome, can I still keep this r-b if I'm going to fix the starvation issue you mentioned in previous patch about lock page? Regards, -- Peter Xu