From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Kosina Subject: Re: [PATCH 0/3] mincore() and IOCB_NOWAIT adjustments Date: Wed, 6 Mar 2019 13:11:39 +0100 (CET) Message-ID: References: <20190130124420.1834-1-vbabka@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20190130124420.1834-1-vbabka@suse.cz> Sender: linux-kernel-owner@vger.kernel.org To: Vlastimil Babka , Andrew Morton Cc: Linus Torvalds , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-api@vger.kernel.org, Peter Zijlstra , Greg KH , Jann Horn , Andy Lutomirski , Cyril Hrubis , Daniel Gruss , Dave Chinner , Dominique Martinet , Kevin Easton , "Kirill A. Shutemov" , Matthew Wilcox , Tejun Heo List-Id: linux-api@vger.kernel.org On Wed, 30 Jan 2019, Vlastimil Babka wrote: > I've collected the patches from the discussion for formal posting. The first > two should be settled already, third one is the possible improvement I've > mentioned earlier, where only in restricted case we resort to existence of page > table mapping (the original and later reverted approach from Linus) instead of > faking the result completely. Review and testing welcome. > > The consensus seems to be going through -mm tree for 5.1, unless Linus wants > them alredy for 5.0. > > Jiri Kosina (2): > mm/mincore: make mincore() more conservative > mm/filemap: initiate readahead even if IOCB_NOWAIT is set for the I/O > > Vlastimil Babka (1): > mm/mincore: provide mapped status when cached status is not allowed Andrew, could you please take at least the correct and straightforward fix for mincore() before we figure out how to deal with the slightly less practical RWF_NOWAIT? Thanks. -- Jiri Kosina SUSE Labs